I have 2 test phones, one I upload the APK to it that with it in "design" mode and the other I uploaded to Google Play in "live" mode. But when I install the live mode from Google Play, and make changes in BT it recognizes the changes. I did not chose publish updates in the control panel so the live mode should not change. any suggestion most appreciated. Thank you, Howard

Hi Howard, So, I have not actually tried the live/design mode yet, but figured I'd help get this conversation started. When you published your app, did the version numbers in your configuration file and control panel match? And did you hit the Publish button so it turned to green? I believe that's the way the updates should get pushed out. Also...keep in mind that until somebody updates their app to a version that has this new feature in the configuration file, they'll see EVERY change you make, because their config file doesn't know about the different modes. Mark

Hi Mark, thanks for writing in. I am not sure if the version number in control panel did match the version number in the config file. But with that said, I would like to ask this question.. If the config file is in "live" mode and run the emulator, should it not see the changes until I hit publish? because even in the emulator it changes without hitting publish. Thanks, Howard

That's a darn good question! I'm not entirely sure!

The version number shouldn't make much difference. The bigger question is, did you re-download the source and recompile the app for the "live" version? If not, it will react like "design" mode.

Hi Howard, I just finished watching the recording of David's recent webinar where he went through the live/design process, and I'm understanding things much better now! @stobe is right - it doesn't appear the version number should make any difference at all. I think it's just a way to keep track of what versions of the live config are published. So, if you have an app version 1.1 published to Apple or Play, a good idea might be to have 1.1 set at the version in your control panel. That way you know what published app version the live configuration is tied to. With respect to your original question, here's how I think it should work: * Make sure you've downloaded new source to ensure you've picked up the code that responds to live/design. * Click Publish in your control panel so that the design configuration and the live configuration are synced (they are the same). * Ensure the currentMode setting in your local configuration file is set to Live, and then compile your app into an apk. This means that the app will respond to any changes to a config file where the currentMode is set to Live. Install this apk to your device (you don't need to go through the store). This is now your "Live App." * Change the currentMode setting in your local configuration file back to Design, and run the app in your Emulator. At this point, the configuration files on buzztouch.com are the same (both live and design), because you haven't made any changes in the control panel. But the app running on the Emulator will respond to the Design version of your configuration file (and the Live App will not). * Make a change in your control panel. If you don't hit the Publish button, you'll see that the Live and Design configuration files are now different. And if an app, be it the live or design version, checks into the reportToCloud URL, it'll only see a change in the design configuration file, and will update accordingly. Since the changes have not been published, the Live App won't see them. In your Emulator, you should see the change you made in the control panel. * Continue to change items in the control panel until you have things looking the way you want. During all these changes, the little icon next to the Publish Changes link should remain red, which means nothing has been written to the Live configuration file. The only device(s) that will see any of the new changes are ones that are running a Design version of the configuration file. * Once all is good, and you're ready to make the changes public to all your app owners, hit the Publish Changes button. That will turn the icon from red to green. At that moment, and at all times when the icon is green, the design configuration file and the live configuration file are the same. So, any changes you had made that earlier were only reflected in the design config file, are now reflected in both. All apps users should see the new content. * As soon as you make another change in the control panel, the Publish Changes reverts back to red, and the only people who see the changes are those running with a design mode configuration file. Phew! Somewhat complicated, but amazingly powerful! Given all this, does it shed any light on what you're seeing with your app? Mark

Hey Mark, thanks for the recap. Unfortunately that is how I originally understood it and have done. But still get the notification that changes have been made to the test phone which should have the "live" settings. This is what I have in the BT_config.txt file and compiled a new apk: "name":"BBAH", "version":"2.3", "currentMode":"Live", I know that it is uploading the newer version, because I see the appropriate version number on the test phone. I am going to try something new and will report back. Fingers cross.

Okay, so I got it to work on another test phone. Perhaps it was the other phone or what I did. This is what I did. Even though it was mentioned that the version number does not matter in control panel and did all this reconfiguration last night so most likely it still does not matter. 1) I changed the version number in control panel to the potential version number that I was going to use in eclipse, ie. 2.3 2) Saved all changes, compile and re-downloaded. 3) Imported into eclipse and changed "design" to "live" in config.txt file. 4) Changed version number to the same version number in BT control panel, 2.3 5) did all usual changes with debugging, etc. 6) compiled to a new apk file. 7) installed it on another test phone through dropbox 8) made changes went back and forth with the test phone and control panel and confirmed it is working as suppose to. Phew, :-) What I am going to do now, knowing that the apk file that I used is working appropiatly, I will try to re-install it on my other phone to see if it is the phone or new apk. Hope that helps h-

Weird! Looking forward to seeing the results of your experiment.

Interesting stuff! Maybe the app on the original phone wasn't getting updated or something. Hard to say. But at least we know it works as designed now. If you see this issue again, we can target our debug a bit more. Great job! Mark

very odd!! I downloaded the APK from google play on a different phone and the "live"/"Design" feature worked. I then installed it on my other phone that i was having problems with from Google Play and it still makes changes without publishing changes AND sees the changes when I publish. I have done it a couple of times and is repeatable. I don't know whats going on! H-

Have you deleted the app from the phone that's not working, and then installed it fresh? What Android version is the "bad" phone running?

Hi Mark, I did delete it and installed it fresh from Google Play. I am using Version 2.3.4 This is what I did and found out! -when I change a custom html/text screen the information changes without publishing the changes -When I change a menu with image screen it does not change without publishing the changes This is very odd. Howard

Actually, that makes sense. The Custom HTML/Text screen is just a web page that resides on the buzztouch servers. So, I can see why you would see the changes without publishing them. But, it may be a bug...I'm not sure it's the best way for it to work. I'll contact @David about it. Mark

So I am not going crazy? :-) well at least about this? h- thanks for contacting @David

Hi Howard, So, this issue with the Custom HTML screen isn't a bug so much as a use case that hadn't fully been considered for this type of screen. David is aware of it now, and is looking at possible solutions. In the meantime, a note will be added to that screen type in the control panel reminding people that changes to the content of that screen (the actual HTML content, not the screen properties) will go live immediately. Eventually there may be Design and Live mode versions of the content. But for now, it should all be considered live. Thanks for helping find this issue! Mark

Hi Mark, awesome to know,and again thanks for looking into it. Howard