View Full Version : Updates install on every single login
killarrow
10-30-2014, 11:21 PM
Every time I login, full set of updates install.
Other than login from scratch, the updates install -
- some times when switching maps
- every time there is a dc and re-connect back
Ign killarrow
Device LG optimus
Os android kit Kat
killarrow
10-31-2014, 12:25 AM
Uninstalled and reinstalled. Now it gets worse, starts loading updates while switching maps.
Waste of time.
yusril
10-31-2014, 12:33 AM
Me to
Ign : mrfirdana
Samsung galaxi tab 10.1
Os android honeycomb 3.2
Finderk
10-31-2014, 07:42 AM
Same problem.
Device = Nexus 7
OS = Android 4.4.4
ArcaneLegendsAddict
10-31-2014, 10:33 AM
Same problem
Ign: ikidl
Device = Lenovo A369i
Os: Android 4.2.2
Samhayne
10-31-2014, 10:53 AM
Hey guys,
We're aware of the issue and working to resolve it. Looks like it will take a new client revisions to fix, so it will take a bit. Our apologies for the issue and thanks in advance for your patience.
barristen
10-31-2014, 11:34 AM
Hi Sam. Do you are saying event is over for is us then? New client approval takes weeks doesn't it?.
Any use even trying to login in that case?
killarrow
10-31-2014, 02:34 PM
I believe it's only for android users this issue exists. Why can't a client update or rollback pushed through without impacting other OSs?
Lenna Drake
10-31-2014, 10:08 PM
I was thinking just me have that proproblem lol but well I hope they fix and I hear about updating in another client, by the way someone know where are the data folder sts.al in android 4.3? Usually the folder was in android/data but don't appear on my phone not in sd card not in internal memory
Haligali
11-03-2014, 05:34 AM
My app started patching when i tried to join to event map, its weird..
killarrow
11-03-2014, 06:37 AM
Hey guys,
We're aware of the issue and working to resolve it. Looks like it will take a new client revisions to fix, so it will take a bit. Our apologies for the issue and thanks in advance for your patience.
Thanks Sam, wrong bug at the wrong time. Appreciate you guys nailed the issue and would be fixing it with next client revision.
Could you give a tentative time for the new client revision.. maybe quantify "so it will take a bit"?
At least we will know how long we will have to live with this issue.