This is the original thread: https://www.buzztouch.com/forum/thread.php?tid=18416E3EA3D3D28E0FAA2E2&fid=06DB0BCB08E3333&sortColumn=FT.id&sortUpDown=DESC&currentPage=2 So I'm still having a problem, when the app starts I get a prompt to refresh. The online and assets config files are synced (copy/pasted from server to assets folder). It's on a self hosted server running the latest update, I don't have the live/development option. This is the BT debug info in Logcat: BT_activity_root:loadAppData loading BT_config.txt from /assests folder in Eclipse project BT_fileManager: readTextFileFromAssets: "/BT_config.txt" BT_activity_root:loadAppData loaded BT_config.txt from /assets folder successfully BT_application: getDataURLFromAppData BT_activity_root:loadAppData BT_config.txt file does use a dataURL for remote updates BT_activity_root:loadAppData cachedAppConfig.txt does not exist in the cache BT_application: validateApplicationData BT_activity_root: application data appears to be valid JSON BT_application: parseJSONData BT_application: parsing core settings BT_application: parsing themes BT_application: parsing tabs BT_application: parsing screens BT_application:parseJSONData done parsing application data Anyone got any ideas of what's going on?

Hey @raveyd, I had the same problem but mine was Buzztouch control panel and the next day it started working again. I wish I could help more because I know how frustrating it can be. Did you try it here on Buzztouch panel? LA

It seemed for a while one of mine was doing that too... it mysteriously stopped. Not sure what to say, other than... procedural plugin removal...? Not sure if it's related, but you 'could' set the apps 'core data configuration URL' to something static. This would feed the same config over and over... see if it's in the device code, or the server wasn't serving something right... Cheers! -- Smug

@LA, you're right, it's frustrating! @Smug, tried the plugin removal, I ended up with just the core files and a simple menu, it was still refreshing! I think I may just remove the report to cloud url, but It's an ongoing app with more content being added. It's doing it with other apps too, but there's an ad network EULA on start up on this app, which is annoying for most users anyway, but with a refresh and the EULA popping up again, it's far too annoying!

It's been happening on my self-hotsed server when testing and developing Android apps. I start the app with a fresh copy and paste of the json data and I still get a re-fresh prompt. I haven't worried too much since it's not a game stopper in my case. I see @raveyd's point though! Let us know if the report to cloud URL fixes it! Cheers Darrel

Hi @ictguy, at least I know it's not just me! (and @LA occasionally!) Like you, I haven't worried about it, perhaps we should have? I can't remember when it started happening which is annoying - is it since the last server update? Running v2.1.7 which I think has been around for a while??

@ictguy - removing the report to cloud url and re-syncing the config file works, but now content can only be updated by submitting a new apk. Guess I can live with it with this particular app.. Frustrating issue though!

This issue seems to be precipitate a crash on some Android devices too. Really need to fix, I'm at a loss. Tim

Funny, I was just thinking about this and a new post pops up! I'm surprised that more people haven't got the same issue, it's not a good user experience, especially if it's force closing too. And it's a horrible user experience when you add in an advertiser EULA that pops up twice on first use. Frustrating.

Yeah, it's throwing errors in the log cat that made me think it's something else causing it. Finally saw the correlation. Grr. Tim

Hi Tim, Could you try this and post back findings? It seems to be working for me, (no prompt to refresh on first load, but a prompt to refresh after I change data) but I have no idea of the ramifications of removing it... In BT_activity_base.java on around line 236. Try removing this: //create a pretend lastModifiedDate file if one does not exist yet... if(!BT_fileManager.doesCachedFileExist(yourappname_appDelegate.cachedConfigModifiedFileName)){ BT_fileManager.saveTextFileToCache("{this is a pretend date}", yourappname_appDelegate.cachedConfigModifiedFileName); } (changing "yourappname" of course! :).

I saw that, almost looks like it was meant to be removed after some debugging by Dave. Might give it a try but really trying to get an app finished, my client is starting to lose patience. I disconnected it from the panel on the Android version to prevent the refresh.