With the new update today the app always crashes at starting.
My device: Samsung Galaxy Nexus (4.1.1)
neumpe, you`ll be probably my savior :). I already see five one star ratings on Google Play, but on non of my devices or close peoples phones that helps me with developing, we have no errors.
So please, may you create for me crash log? Best is to use CatLog program, install it and immediately after crash, start is and from menu choose "send" and send me this log on email@example.com!! I`ll immediately fix it and release new version! Thanks
My CatLog programm doesn`t record anything, but I have sent you a google bug report.
I`m already looking at it. I don`t like these google reports because there is usually only a plain error without any description, but here it`s pretty clear
java.lang.UnsatisfiedLinkError: Couldn`t load mylibrary: findLibrary returned null
for unknown reason, Locus have problems with loading base c++ library. As I found on internet, it`s probably some bug in android. I`ll try to release new version with recompiled library so I`ll be glad for report if all is ok or not. Thanks
nuempe, may you please install and test this version? Are you using Pro right?
This is version prepared for release but I want to be sure, it will work. Thank you!
Yes I use the pro-version. But the version 2.5.6 has the same issue.
damn ... it`s probably some issue in Android and seems I cannot fix it from my side ... try this: please go to list of applications and "clear cache", or "clear data" in Locus
please second try https://dl.dropbox.com/u/8015949/Locu... !
I`m desperate ...
1. Nothing has changed in this version around handling of C library.
2. This issue is only on A4.1
3. nowhere cannot be found and info about such issue, so I at least created
4. report on Android NDK Google site https://groups.google.com/forum/?from...
Did you solve it yet? I tried deleting cache, deleting data and installing 2.5.6b, but it still crashes immediately. :(
//aah, I see, I updated to newer version at Google Play and it crashed again. So I deleted data and it worked! Then I recovered data using Titanium Backup and it still works! :-)
damn it`s stupid. No it`s not solved and seems that only solution is to DELETE DATA or RE-INSTALL. Still no idea why this happen, mainly because I have also 4.1.1 and this is not happening to me, so it`s much harder to debug...
seems that Locus is not alone ...
did you also read this?
apparently google updated googleplay again today and the jellybean issue should be gone. had something to do with the lousy new copy protection.
hmm nice. It`s not exactly same problem but seems that their new "copy protection" mechanism also affect Locus libraries. If it`s really disabled in new market version, then update should works correctly now. Problem is that this affect only some of 4.1.1 users, not all .. anyway thank you for interesting information. Sad that I cannot react on comments on market ...
Finally some good news from Google
Dear Google Play developer,
We have identified one or more of your applications as being affected by a recent issue in Google Play that prevents some users from launching your app. To resolve the issue, you need to publish an update as soon as possible. This will cause your users to receive an update, which will fix the issue.
The underlying cause was an error in the Google Play update logic that resulted in native libraries being incorrectly installed during updates of affected applications for users running Android 4.1 (Jellybean), who installed an update of your application between August 1 to August 5. This affects a small minority of applications, specifically non-forward-locked paid applications that use the NDK and native libraries.
No change to your application is required. Simply increment your versionCode in your Android manifest file, generate a new APK, and publish it through Google Play.
We apologize for the inconvenience this has caused you and your users. The underlying cause has now been rectified, and steps have been taken to ensure similar issues don`t arise in the future.
The Google Play team
Replies have been locked on this page!