i have a problem with flurry for android. I don't see last app version in filter several days (about 5 days). Later new version got to version list in filter very fast.
Also if check "TOP 10 VERSIONS BY ACTIVE USERS" i can suppose that my new version is saved as other. I upload new version 20 march and on graph i see that version other grow from 20 march.
I use SDK version 6.6.0. Now i upgraded to 6.9.2. Later flurry determined version of app without problem.
For init flurry i use the following code:
new FlurryAgent.Builder()
.withLogEnabled(true)
.withListener(getFlurryAgentListener())
.build(context, MY_API_KEY);
Can anyone say what i do wrong or how to solve this problem?
Your app has more than 1000 app versions.
To correct this you will need to delete some older versions you no longer need.
Currently this can only be done in the old 'Flurry Classic' site. See here:
We will be adding this feature to the new Flurry site soon.
Finally you can avoid problems with the version limit by using separate project api keys for development/testing versus the published version of the app.
Related
We have given two new updates in the last 15 days.
but still for some users its showing the older version of App.
We have increased the version code and version name with every update.
But for some devices still, it's showing the older version.
Here is the Scenario for the issue
The latest app is updated on 19 June
1.For the first time, the app store shows the Older version
version Code: 207
2.After that when user visit to play store again
and search for the same App it shows
the next updated version.
version Code: 209
3. Again After that when user visit to play store
and search for the same App it shows
the latest updated version which is on 19th of june
version Code: 212
We always upload the signed apk on Playstore.
Why it's not showing the latest update for the first time install.
Please help us with this
Thanks in advance
From Play Console support:
Due to device connectivity and varying server load, it
may take several days (in some cases a week) for app updates to reach
all devices. The behavior you are seeing with the update being
available on the web is common for apps. The mobile store will update
in due course.
Recently I noticed that very old app version (released 3 months ago) is being showed in the “Latest release” dashboard. It looks very strange because normally when I’m releasing new app version then the oldest version adoption count decreases almost to zero after some time. But adoption count of this version is always about 10 percent per those 3 months.
Also other strange things for this version are:
daily user engagements is ~60 min or more when normally for other version it is ~8min.
sessions count is about ~500K when normally it is ~20K
all sessions country is US only when normally app is supported in 14 countries
every day active users for this version shows up to 10 users and all of them are from US
when I‘m seeing over "StreamView" then this version users devices are not recognised. It is being showed as “Unknown device”.
This old app version didn’t have any major changes and also with next app version everything was fine, so I don’t think, that the problem is in app.
Do you have any thoughts about what could be here or maybe do you have any experiences with that?
thanks for any advices.
The answer is in the tooltip:
The problem is with the unusual data representation: Firebase shows the version of the active users.
Therefore your "strange users" are people who are using your app regularly, but haven't updated it to a newer version yet.
Several apps are recently solving this issue with manual version checking, and if the version is old, a screen with update app information is shown.
I'm trying to update my app to the Google Play Store. I have the current version number of the app set to 2000000000 and would like to update it to 2000000001. Please don't ask my why there are such version numbers chosen.
I got this error message when I try to push the new version: "Upload failed
The version code of your APK is high and you risk not being able to update your APK.". The one thing I don't understand is that according to official google documentations the max version number is MAXINT, 2147483647, so I still have roughly 150 000 000 versions left. The other thing is, I managed to update other app with the same version numbering convention, the app is on the same dev account and I have no such error at all.
I checked all the numbers couple of times to be sure I'm not doing some stupid typo. I also already contacted Google support but maybe someone here have some kind of solution?
Google support responded to my requests. They changed the maximum available version code to 2000000000 and didn't update the documentation at the time I was posting this question (right now it is still MAXINT: 2147483647). Quite an edge case here but maybe someone will find this useful.
Looks like there was an update 08/11/2016 (UTC) in the docs. Not the old MAX_INT value or the 2000000000.
Warning: The greatest value Google Play allows for versionCode is 2100000000.
My Unity app had a high version code (not sure where from), I added version 3 and version code 3 in the Unity app, and that shut Google Play :) There is a crafty version for build.gradle though Unity 3D: What is the Android Bundle Version and Version Code and how do they relate?
My application is not submitted in Play store. Its a non market app, each time when we give an update, the application checks by its own and will download the latest build from our own server.
I have released application to my clients, for around 4 times. Each time i have
increased the version code from 1 to 4.
In my latest build i have not incremented the version code to be as 5, now i am getting a complaint from my client side that the new update is not able to be installed.
Whereas when i tried in my local device, its working good.
Does the version code affects the installation of updating a build
Yes exactly, version code effects the market build.
According to you, your code is checking on your server of a possible update via version of the app. As you have not incremented the version of the app this time, there is possible chance of error. Rest all depends upon your code. As far as google play is considered, you have to increment the version code each time you upload a new apk
I need some clarifications on Android. For example I developed an application with min version of 2.3.3 and I uploaded to play store and next versions I mean coming versions was Implemented in min 4.0 because functions force me to do that. So How Play store will response ? Is it consider like new project or some thing else? What will happen for already installed 2.3.3 version user? Can any one explain this?
if you change the min SDK then users that dont have above 4.0 will not be able to get new versions of your app and they will be stuck on the version they have until they get a new device that meets you minimum sdk.
Its not a new project all you are doing is updating you current one