I wrote a super simple android app for a conference using phonegap and jquery mobile. At the last minute, there was a room change. At the time, I had all of the info in the html file, so I could only update it by deploying a new version of the app and hoping everyone updated. How can I make this better for next time? I know I could store the info remotely in an xml file and download it, but I don't want to needlessly use up their data if nothing has changed. What is an efficient way to do this?
Thanks
Just have a super simple service which your app contacts every now and then if there are updates available and if so then download the new infos ... I would say ;-) More elaborate would be using some push services like parse.com offers.
You could host the project on a GIT or SVN repository, and then just tell them to check out/clone your project at the beginning of each session.
That way you can confirm and be sure that they are all running what you want them to run.
Related
Finally after a lot of hassle I released my first Android application after migrating from C# to Java :-)
But now I get duplicated notifications on devices where I've debugged my application before finishing coding.
All other users who installed my application after its release get the push notifications properly without any duplication or any kind of problem.
"After googling & searching I found out that this problem only exists on older Parse.com SDK, but it's weird since I'm using the latest one!"
I've been wondering about two things:
Will other users face the same problem after I release an update? ( Version code will be updated - And I'm not using any store, I maintain the updates on a private server & got my own code to do the update process ).
How can I solve this problem? I was thinking about creating a new application entry on my Parse.com account for every single new update ( If I'm sure that there isn't any solution ).
Any help would be appreciated.
After extensive testing & checking ..
I found a proper solution, may be good for some, but a lot will not like it.
It's a bug in Parse's SDK itself as I guess, when you delete the application from a device, it won't delete its record from the database. So, when the app is installed again, the same device will have two different records. So it gets 2 duplicates .. The number grows as much as you uninstall/install!
My solution is to increase the version code and change the version, so it'll be considered as a new application by Parse with new records!
recently, I've started the developing of a new app, and this app is in need of constant update. I know I can do it with alarms, but I think that a better way is to add my app to android automatic sync service (the one that is added gmail app and whatsapp for example).
I've looked for that topic, but couldn't find any answer about how to interact with that service. Can anybody provide me an example of how to accomplish it?
Thank you so much,
Vyrphan
Check out the SampleSyncAdapter code under the SDK samples. It will be in a directory akin to;
C:/Program
Files/Android/android-sdk/samples/android-10/SampleSyncAdapter/
Maybe this can help you http://developer.android.com/training/cloudsync/index.html
I'm trying to build an application which requires bedework as the backend calendar server, but am unable to get relevant documentation to set it up. Furthermore, I need to understand the mechanism to use it with android.
Don't know anything about bedework in specific, but the docs are here http://www.bedework.org/bedework/update.do?artcenterkey=36 and you can download what you need here: http://www.bedework.org/bedework/update.do?artcenterkey=2. Once you have it, presumably the JAR file, just drop it in your app and do what you want with it..
I wonder if anyone can tell me if it is possible to save an android app on a server and use the RSE Eclipse plugin to edit it ?
This has become necessary for me so I don't have to physically be at work to continue work on a project.
Thanks for any input.
Sorry if this seems obvious...but is there no way you can work on the app locally and save your changes to the server using RSE...or even better, commit the changes using some version control system?
So, I have found a bug in a specific sdk that causes it to fail on some Android phones after re-installing a new version of an app which uses the sdk (via adb install -r, and presumably when a user gets an update that has been pushed to the Android market). Is there any way to force an application's data to automatically be cleared upon update of the app? I realize there are different ways that data could be stored, but I just need to essentially simulate an invocation of the "Clear Data" button that'd you find when browsing to the application in the "Manage Applications" section of the Settings (i.e. I just want all data gone).
I am an Android noob and am doing minimal Java coding on this project, so I am basically looking for the simplest solution here. I suppose I could settle on storing a "currentVersion" to disk and then checking it upon launch every time to see if the real current version matches the version that was written to disk on the last launch. Is that the only real way to do this? If so, what's the simplest way to do so?
Thanks!
Is there any way to force an application's data to automatically be cleared upon update of the app?
No, at least for my definition of "automatic".
I suppose I could settle on storing a "currentVersion" to disk and then checking it upon launch every time to see if the real current version matches the version that was written to disk on the last launch. Is that the only real way to do this?
I'd name it lastKnownVersion, but otherwise this approach seems sound and probably is your only viable option.
If so, what's the simplest way to do so?
Ummm...do exactly what you said. Use Java I/O (storing the file somewhere inside of getFilesDir()), or SharedPreferences.
Bear in mind, though, that your users may get rather frustrated if you blow away their data on an app update. Personally, I'd rather we find a better solution to your original problem ("I have found a bug in a specific sdk that causes it to fail on some Android phones after re-installing a new version of an app which uses the sdk").