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!
Related
I have published an application to Google Play store. Now I have update ready, the application uses some serialized objects and the update has changed them a bit, therefore an uninstall before updating is needed.
How do I force users to uninstall the application first or do I have to work this out in code somehow?
I think you should work this out in code. Figure out a way of identifying the old data and converting/upgrading it to your new structures if needed/possible. Even keeping the old object defs around for reading and then converting these in memory to the new structure should work.
One option would be to write some kind of "schema version" pref that at least tells you what the data was written under (missing that pref means it is version 1). At least it will be easier next time.
BTW, the reason I recommend this over just deleting the files is the risk of just repeatedly deleting the files. You need some way of detecting that the files that are there are old (ignorable, deletable or for upgrade) or new and should be kept.
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.
I am a beginner in Android, this is my first app in Android and I stuck very badly, I need your kind help.
Here is the problem statement.
We have a very huge database in MySQL, I need to do authorization with
an android app and on successful log in i need to display all the
order details of that logged in user.
So to do this I have used PHP for the backend work like, authorisation, displaying the order for that user and updating. Unknowingly I worked with ANdroid 2.2(Floryo) version. All these functionalists are working fine with Android 2.2 version but when I try to run the same with Android 4.0 then it giving me runtime error. I am getting the response in terms of JSON from a PHP script file.
What is missing in this case. Do I need to install any library.
Please help me out. After getting the work done also I am unable to show my work.
Check with SQl problem first, i think sqlite version is different in Android2.2 and Android4.0, some queries work differently in this, I know my answer to your question is half.
I've written a program that, when completed, I plan to add to the Android Marketplace. I have given many files as features for users to store information and reload later, and while debugging, I've noticed the files tend to get deleted when I update the code after a long while (like a few days spread apart--for some reason, it doesn't happen when I update the code often, like every hour when I'm adding new features and testing them out). Note that I use a real phone for testing and not the emulator. What I'm wondering is, will the files get deleted after each release of the app?
I really don't want users to lose their stored information on every update or bug fix I provide, so if that is the case, is there a way around this?
Nope the files doesn't get deleted automatically, but it depends upon where you are storing the files. If the user deletes the app the files associated with it will get deleted too. But in case of an upgrade, No! normally it won't.
In case you are using SQLite for storing data, there is a proper way to handle upgrade there.
Periodically I'd like to make very minor changes to an app on the market, that don't justify notifying users that they need to upgrade. For instance a little cosmetic tweak. Basically I don't want anyone (including my client, for whom I built the app) to notice that I made the change, but I'd like all new downloads to get the changes. Can I do this, or will making any changes cause everyone to be alerted there is a new version?
I understand where you're coming from but this is a very bad idea. If it were possible you could have a bunch of people with the same version numbers but a different program making it very difficult to track if something goes wrong.
You can however increment only the integer version and leave the text version the same (this only shows in the market anyway).
This will still cause people to get auto updates for your app. I think you should either bundle all your changes up and wait or just accept that everyone will be getting lots of updates for your app.
Unfortunately Prashant's answer is not correct. You only need to increment the code, not the human readable version string.
I frequently leave the user visible version number alone when releasing minor tweaks and bug fixes, saving the market visible version numbering for actual features and major bug fixes.
Well last time i tried to the same thing, i got a message that application version numbers needs to be incremented before uploading a new version of the application. Also, version number and version code need not be in sync. But both needs to be incremented before uploading the new apk in market place. Hope this helps.