Fixed
Status Update
Comments
hb...@gmail.com <hb...@gmail.com> #2
Question from another developer:
You mention ".. fail to install either from the market or directly from an .apk"
My understanding of the partial apk upgrade functionality was that it was part of the Play Store client so it didn't have to download the whole application and could save bandwidth. If you are adb'ing the apk or launching the apk from the device then the partial upgrade functionality shouldn't be being triggered as there is no bandwidth to save. Unless the package manager has had more far reaching changes..?
You mention ".. fail to install either from the market or directly from an .apk"
My understanding of the partial apk upgrade functionality was that it was part of the Play Store client so it didn't have to download the whole application and could save bandwidth. If you are adb'ing the apk or launching the apk from the device then the partial upgrade functionality shouldn't be being triggered as there is no bandwidth to save. Unless the package manager has had more far reaching changes..?
ex...@gmail.com <ex...@gmail.com> #3
Thanks for your comment. I guess that's true. So it must be something else in 4.1.1. Too bad we have no access to a Nexus here in Europe so I can see it for myself.
hb...@gmail.com <hb...@gmail.com> #4
Dunno. I've just pushed a new version of my app and within an hour I had a user email me with the app crashing on startup. Turns out he does use Jelly Bean, I do have native code in my app and I guarantee I have not changed it or touched the .so files in any way. I use ACRA in my app and ACRA did not get triggered despite it being one of the first things activated in the Application.onCreate(). So that would indicate something failed to instantiate my Application class - and guess what...my Application class tries to load a native library as part of a static initialiser.
Unfortunately the user uninstalled and reinstalled and that fixed it, so I couldn't get any logs back to confirm if it's the same bug. But it sounds far too coincidental...? (Though with the changes to READ_LOGS in JB, it's unlikely I would have been able to get any decent logs back anyway).
If this is a bug with the Play Store or the partial apk functionality, there's no way to test it on the emulator as I'm sure adb uploads the whole apk and pm installs the whole thing. And as usual, there's no 4.1.1 emulator image to test either.
Unfortunately the user uninstalled and reinstalled and that fixed it, so I couldn't get any logs back to confirm if it's the same bug. But it sounds far too coincidental...? (Though with the changes to READ_LOGS in JB, it's unlikely I would have been able to get any decent logs back anyway).
If this is a bug with the Play Store or the partial apk functionality, there's no way to test it on the emulator as I'm sure adb uploads the whole apk and pm installs the whole thing. And as usual, there's no 4.1.1 emulator image to test either.
me...@gmail.com <me...@gmail.com> #5
Hi,
after today update, I have absolutely same problem. After update I already received around 100 reports on Developer console with exactly same issue
I tried to rebuild library with new NDK 8b and update version on Google Play, but same problem. Re-install or "Clear Data" seems to be only solution. Any advice is more then welcome! (and any advice is very valuable in this case)
after today update, I have absolutely same problem. After update I already received around 100 reports on Developer console with exactly same issue
I tried to rebuild library with new NDK 8b and update version on Google Play, but same problem. Re-install or "Clear Data" seems to be only solution. Any advice is more then welcome! (and any advice is very valuable in this case)
ex...@gmail.com <ex...@gmail.com> #6
I'm so glad I'm not alone in this and that I have posted this bug report. Hopefully someone at Google reads these, lol! And of course users are blaming me, which I can understand.
I also use ACRA and I do get ACRA reports of this bug. I also did install the NDK version 8b to no avail.
For now, I try/catch System.loadLibrary() and if it's Android Build 16 or higher and an exception is thrown, I pop up a dialog stating that due to a bug in JB, they need to re-install from market. Doesn't solve it, but it gets rid of most bug reports and questions until it gets solved.
I also use ACRA and I do get ACRA reports of this bug. I also did install the NDK version 8b to no avail.
For now, I try/catch System.loadLibrary() and if it's Android Build 16 or higher and an exception is thrown, I pop up a dialog stating that due to a bug in JB, they need to re-install from market. Doesn't solve it, but it gets rid of most bug reports and questions until it gets solved.
me...@gmail.com <me...@gmail.com> #7
Hmm good idea with try-catch. I have some core feature in this lib (probably as well as you), but this can at least help a little. Blaming on market for 4.8 rated app is really stupid experience.
Good luck - probably to both of us :)
Good luck - probably to both of us :)
en...@google.com <en...@google.com>
me...@gmail.com <me...@gmail.com> #8
is there a way to confirm that this issue is related to new "Copy protection" system and also to this bug? http://code.google.com/p/android/issues/detail?id=34880
Some! users (I have no problem on my Nexus so I cannot report precise information) have just problems with retrieving "armeabi" library that is for sure there. Is copy protection mechanism also affecting this is any way? I think so ...
Some! users (I have no problem on my Nexus so I cannot report precise information) have just problems with retrieving "armeabi" library that is for sure there. Is copy protection mechanism also affecting this is any way? I think so ...
pa...@gmail.com <pa...@gmail.com> #9
Exact same problem here! Updated a keyboard a few days ago and got loads of crash reports from Jelly Bean users (Nexus 7, Galaxy Nexus and Xoom). The update caused a problem with loading a native library (it just couldn't find the lib after the update). However, the update went well on all other devices. Also, and this is the weirdest part... A fresh install fixed the problem for all JB users that run into this issue. Lol, was a big update nightmare.. Have to hold back updates now.. totally no idea how to fix this.
The error report was:
java.lang.UnsatisfiedLinkError: Native method not found
Caused by the fact that the native library wasn't loaded (that error is catched by the app so no report on that)
The error report was:
java.lang.UnsatisfiedLinkError: Native method not found
Caused by the fact that the native library wasn't loaded (that error is catched by the app so no report on that)
ap...@gmail.com <ap...@gmail.com> #10
Does this happen with paid apps or also with free apps? Sounds like what menion said - the issue with app encryption introduced in Jelly Bean.
For me, paid GoLauncher, PowerAMP etc skins, which use the assets folder won't function because the entire folder seems removed.
Prior to this app encryption "feature", I was having similar issues with "Copy Protection" in the Developer Console. Enabling it causes the assets folder to go missing. Pulling the apk from the data/app folder (still unencrypted) confirmed it to be the case.
For me, paid GoLauncher, PowerAMP etc skins, which use the assets folder won't function because the entire folder seems removed.
Prior to this app encryption "feature", I was having similar issues with "Copy Protection" in the Developer Console. Enabling it causes the assets folder to go missing. Pulling the apk from the data/app folder (still unencrypted) confirmed it to be the case.
pa...@gmail.com <pa...@gmail.com> #11
Can anyone confirm that this is working again now Google has temporarily turned off app encryption ? I need to fix a issue in my app, but definitely don't want to open the gates of hell again :P
ek...@gmail.com <ek...@gmail.com> #12
Google didn't turn off anything. I can still reproduce the issue with Android 4.1.1 and the last Play Store version (3.7.15).
pa...@gmail.com <pa...@gmail.com> #13
So it is still existing? Well seems like a major problem then. @ekera.. how did you reproduce the problem. Did you create an experimental app for this? I mean, this doesn't seem something you can experiment with with paying customers.
ek...@gmail.com <ek...@gmail.com> #14
I replied to the question about the app encryption. However I don't test it the way it is described here, I just verify paid apps malfunction (widgets that disappear etc.) like it has been reported for Issue 36949180
me...@gmail.com <me...@gmail.com> #15
finally some good news, thanks Google team. If you don't mind, I'll publish email I just received just to notify also others about this issue
----------------
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.
Sincerely,
The Google Play team
----------------
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.
Sincerely,
The Google Play team
pa...@gmail.com <pa...@gmail.com> #16
Thanks menion, for posting this. Finally, back to work! Yay
di...@android.com <di...@android.com> #17
Is it ok to close this bug now?
ex...@gmail.com <ex...@gmail.com> #18
Yes, it can be closed, thanks
ex...@gmail.com <ex...@gmail.com> #19
Yes, it can be closed, thanks.
pa...@gmail.com <pa...@gmail.com> #20
Agreed, can be closed. I can confirm that the bug is fixed.
ov...@gmail.com <ov...@gmail.com> #21
Hi
I think that the problem is not solved yet, because I'm still encounter this issue on a XOOM tablet with 4.1.1.
Here is the use case:
I'm installing the current version of the app from Google Play then after I am updating with the new release candidate(just a regular APK install from external memory) I got this error with a native library load. If I'm just doing a fresh install of release candidate all works just fine.
The application on Google Play is free and does have copy protection on.
I think that the problem is not solved yet, because I'm still encounter this issue on a XOOM tablet with 4.1.1.
Here is the use case:
I'm installing the current version of the app from Google Play then after I am updating with the new release candidate(just a regular APK install from external memory) I got this error with a native library load. If I'm just doing a fresh install of release candidate all works just fine.
The application on Google Play is free and does have copy protection on.
en...@google.com <en...@google.com> #22
this bug is fixed, and the fix released. @21 appears to be bug 36949180 , not this bug.
ov...@gmail.com <ov...@gmail.com> #23
I'm not sure that the bug here http://code.google.com/p/android/issues/detail?id=34880 is the one I encounter. First the issue is not happening because of google play install. I'm just installing using an APK on device.
Should I open another issue for this? Because the problem is still there.
Should I open another issue for this? Because the problem is still there.
me...@gmail.com <me...@gmail.com> #24
I have update application on Google Play around three days ago and since then, no more similar reports in dev console. So from my side, issue is fixed.
Thanks!
Thanks!
ja...@gmail.com <ja...@gmail.com> #25
Hello, We have this problem on our app, it crashes when the users try to update on android 4.1.1. We made a workaround by moving the ".so" file ourselves, but the problem is that , when the user installs the update, sensible data is being deleted ( user's profile ).
How can we solve this issue without uninstalling our app?
How can we solve this issue without uninstalling our app?
mo...@gmail.com <mo...@gmail.com> #26
Code1024
22...@gmail.com <22...@gmail.com> #27
ca...@gmail.com <ca...@gmail.com> #28
hotspot it was working normaly on my galaxy s 3 .
after i upgrade my frimware via samsung kies , all the vpn application is stop working ( hotspot - one vpn click - hidenman ) .
please any one kindly can advice me ?
after i upgrade my frimware via samsung kies , all the vpn application is stop working ( hotspot - one vpn click - hidenman ) .
please any one kindly can advice me ?
ra...@gmail.com <ra...@gmail.com> #29
My elite subscribion wouldn't show. Help
Rasikh.n@gmail.com
Rasikh.n@gmail.com
yo...@gmail.com <yo...@gmail.com> #30
es...@gmail.com <es...@gmail.com> #31
c....@gmail.com <c....@gmail.com> #32
The problem mentioned above happened today in my application, too.
(Some users can't access .so file.)
This only happens to some android 4.1.1 devices.
Does this problem reoccur?
(Some users can't access .so file.)
This only happens to some android 4.1.1 devices.
Does this problem reoccur?
ex...@gmail.com <ex...@gmail.com> #34
Recently I had this report again. The customer upgraded his phone to a newer Android version and couldn't run the app anymore because of missing libraries. Perhaps the 'app optimization' step optimized it away??
hi...@gmail.com <hi...@gmail.com> #35
Is this problem caused by a bug of Android 4.1.1 ?
In which version will this problem fixed ?
In which version will this problem fixed ?
c....@gmail.com <c....@gmail.com> #36
I'm still suffering from this problem.
I think the causation is different from #15.
The following two issues are also similar with my app's problem.
https://code.google.com/p/android/issues/detail?id=37833
https://code.google.com/p/android/issues/detail?id=46074
I released the previous version of my app with copy protection ON, and released new version with not selecting copy protection feature in Jun 2013, because copy protection feature is not available in the Developer Console after Feb 2013.
Is this problem caused by a bug of Android 4.1.1?
I think the causation is different from #15.
The following two issues are also similar with my app's problem.
I released the previous version of my app with copy protection ON, and released new version with not selecting copy protection feature in Jun 2013, because copy protection feature is not available in the Developer Console after Feb 2013.
Is this problem caused by a bug of Android 4.1.1?
b....@gmail.com <b....@gmail.com> #37
Could this please get increased attention from the android team?
This is still happening. I have 269 reports this week show up in Developer Console.
I've seen this issue for a long time now, in my free non-drm app.
So it is not DRM related.
It also happens to a wide range of different devices, across all manufacturers.
I wonder if this happens to users that run multiple user accounts on their device?
Did multiple-user account get introduced to Android roughly at the same time as the reports?
This is still happening. I have 269 reports this week show up in Developer Console.
I've seen this issue for a long time now, in my free non-drm app.
So it is not DRM related.
It also happens to a wide range of different devices, across all manufacturers.
I wonder if this happens to users that run multiple user accounts on their device?
Did multiple-user account get introduced to Android roughly at the same time as the reports?
de...@gmail.com <de...@gmail.com> #38
In addition to #37:
After having talked with another developer about this issue I assume the following:
When an incremental update gets installed from Google Play, the native library paths are changed into "<packagename>-2" (dash two) probably in order to point to updated libraries.
These changed paths are visible in some of the crash reports. However, sometimes native libraries do not change with an update and I assume that the Google Play backend does not re-bundle these unchanged library files with an incremental update APK.
Now here are two possibilities in terms of this UnsatisfiedLinkError: either the "<packagename>-2" paths are real directories containing library files or they are just symlinks. If they are real directories then they must contain all library files for the currently installed version of the app. Original ones from the first installation and the updated versions. If a native library did not change between original installation of the full APK and the incremental update then it may be missing in the "-2" directory. If these "-2" directories are just symlinks then they point at the wrong file system locations.
Either way, the update / installation routine for native libraries can go wrong and seems to go wrong quite a lot.
It would be great if the Google Play APK installer would verify that the installation of all native libraries worked correctly. In case of an installation error it should silently re-install the full APK version without forcing the user to uninstall first in order to avoid data loss.
Unfortunately I believe that this issue tracker here is the wrong place for reporting this problem. It probably should be communicated to the Google Play development team.
After having talked with another developer about this issue I assume the following:
When an incremental update gets installed from Google Play, the native library paths are changed into "<packagename>-2" (dash two) probably in order to point to updated libraries.
These changed paths are visible in some of the crash reports. However, sometimes native libraries do not change with an update and I assume that the Google Play backend does not re-bundle these unchanged library files with an incremental update APK.
Now here are two possibilities in terms of this UnsatisfiedLinkError: either the "<packagename>-2" paths are real directories containing library files or they are just symlinks. If they are real directories then they must contain all library files for the currently installed version of the app. Original ones from the first installation and the updated versions. If a native library did not change between original installation of the full APK and the incremental update then it may be missing in the "-2" directory. If these "-2" directories are just symlinks then they point at the wrong file system locations.
Either way, the update / installation routine for native libraries can go wrong and seems to go wrong quite a lot.
It would be great if the Google Play APK installer would verify that the installation of all native libraries worked correctly. In case of an installation error it should silently re-install the full APK version without forcing the user to uninstall first in order to avoid data loss.
Unfortunately I believe that this issue tracker here is the wrong place for reporting this problem. It probably should be communicated to the Google Play development team.
en...@google.com <en...@google.com> #39
this is fixed in jb-mr2.
[Deleted User] <[Deleted User]> #40
Out of curiosity, since the issue has been diagnosed (and fixed) is there any work around?
With the release schedules of manufacturers and carriers, it will likely be many months before customers are on jb-mr2 and we currently have hundreds of users crashing currently every time they upgrade. We tried changing the library name like was suggested in comment #38 , but that did not resolve the issue.
With the release schedules of manufacturers and carriers, it will likely be many months before customers are on jb-mr2 and we currently have hundreds of users crashing currently every time they upgrade. We tried changing the library name like was suggested in
dn...@gmail.com <dn...@gmail.com> #41
[Comment deleted]
de...@gmail.com <de...@gmail.com> #42
I got to agree with #40. This problem is not fixed for us developers and users of that faulty Android version. It would be great if you could provide us with more details and a workaround solution for this problem.
al...@gmail.com <al...@gmail.com> #43
I still have the same problem and watching at the crashes in the dev console it's happening mostly on 4.2.
iv...@gmail.com <iv...@gmail.com> #44
I have the same problem: (id=com.foobnix.pdf.reader)
Breakdown for all 29 reports (this week)
Android 4.2 21 72.4%
Android 2.3.3 - 2.3.7 4 13.8%
Android 4.1 4 13.8%
by device
Galaxy Note 8.0 (kona3g) 11 37.9%
Xperia L (C2105) 7 24.1%
ITP-R208W (rk30sdk) 3 10.3%
ZTE V791 (P175A40) 2 6.9%
...
Thanks
Breakdown for all 29 reports (this week)
Android 4.2 21 72.4%
Android 2.3.3 - 2.3.7 4 13.8%
Android 4.1 4 13.8%
by device
Galaxy Note 8.0 (kona3g) 11 37.9%
Xperia L (C2105) 7 24.1%
ITP-R208W (rk30sdk) 3 10.3%
ZTE V791 (P175A40) 2 6.9%
...
Thanks
pa...@gmail.com <pa...@gmail.com> #45
Is this still an issue??? Are you guys sure that it is this issue?
iv...@gmail.com <iv...@gmail.com> #46
>Are you guys sure that it is this issue?
Yes, I have publish new release and find:
java.lang.UnsatisfiedLinkError: Couldn't load xxx from loader dalvik.system.PathClassLoader[dexPath=/system/framework/multiwindow.jar:/data/app/com.foobnix.pdf.reader-2.apk,libraryPath=/data/app-lib/com.foobnix.pdf.reader-2]: findLibrary returned null
for Galaxy Note 8.0
I have total more than 1000 crashes with this error, for last week more than 30
It's affect maybe 0.01% percent of devices, but the problem still exist.
I can share dev console for Google Dev if need but I think they should have global crash reports and know about this issue.
Yes, I have publish new release and find:
java.lang.UnsatisfiedLinkError: Couldn't load xxx from loader dalvik.system.PathClassLoader[dexPath=/system/framework/multiwindow.jar:/data/app/com.foobnix.pdf.reader-2.apk,libraryPath=/data/app-lib/com.foobnix.pdf.reader-2]: findLibrary returned null
for Galaxy Note 8.0
I have total more than 1000 crashes with this error, for last week more than 30
It's affect maybe 0.01% percent of devices, but the problem still exist.
I can share dev console for Google Dev if need but I think they should have global crash reports and know about this issue.
al...@gmail.com <al...@gmail.com> #47
Exactly the same here. After the last update of our app I've seen a considerably increase of the crashes due to this issue. For what I can see in the google play console the xperia phones seem the most affected devices.
hi...@gmail.com <hi...@gmail.com> #48
I also encountered this issue and found the reappearance condition.
- OS is only Android 4.1.1 (It doesn't occar on 4.0.x or 4.1.2)
- App contains native library.
- Previous version of App was installed with copy protection mode.
(Copy protection was abolished on Google Play in Feb 2013. You can make similar status by "adb install -l [apk file]")
- Next version of App is updated through Google Play.
It seems that this issue is caused by a bug of Android 4.1.1.
You can avoid this issue by any of the following.
a) Once remove the App and reinstall it.
b) Update Android to 4.1.2, 4.2.x or upper.
I hope this will help.
- OS is only Android 4.1.1 (It doesn't occar on 4.0.x or 4.1.2)
- App contains native library.
- Previous version of App was installed with copy protection mode.
(Copy protection was abolished on Google Play in Feb 2013. You can make similar status by "adb install -l [apk file]")
- Next version of App is updated through Google Play.
It seems that this issue is caused by a bug of Android 4.1.1.
You can avoid this issue by any of the following.
a) Once remove the App and reinstall it.
b) Update Android to 4.1.2, 4.2.x or upper.
I hope this will help.
pa...@gmail.com <pa...@gmail.com> #49
Thanks hisas... ! Much appreciated.
al...@gmail.com <al...@gmail.com> #50
For what I can see in our crash report console, this happens on almost all the android versions:
2.3.x, 4.0.x, 4.1, 4.2 and 4.3 ( on 4.3 it's 83% of the times ).
Moreover, we never had the copy protection enabled on our app.
Most affected devices:
Xperia L 75%
Optimus L3 6%
Galaxy S2 Plus 3%
2.3.x, 4.0.x, 4.1, 4.2 and 4.3 ( on 4.3 it's 83% of the times ).
Moreover, we never had the copy protection enabled on our app.
Most affected devices:
Xperia L 75%
Optimus L3 6%
Galaxy S2 Plus 3%
dn...@gmail.com <dn...@gmail.com> #51
This issue has been closed and marked as released. We still see reports for users in 4.2 and 4.3.
mi...@gmail.com <mi...@gmail.com> #52
I have same problem with user on Galaxy Note 8.0 - 100% crashes
sv...@gmail.com <sv...@gmail.com> #53
This issue is not fixed. Problem still exists on different versions of Android.
al...@gmail.com <al...@gmail.com> #54
So if this bug is marked as solved, why in the chromium code there's a workaround to load native libraries?
http://src.chromium.org/viewvc/chrome/trunk/src/base/android/java/src/org/chromium/base/library_loader/LibraryLoader.java
and if you look at the comments:
"PackageManager may fail to update shared library."
So, are you planning to fix this issue?
and if you look at the comments:
"PackageManager may fail to update shared library."
So, are you planning to fix this issue?
di...@squareup.com <di...@squareup.com> #55
[Comment deleted]
sh...@gmail.com <sh...@gmail.com> #57
java.lang.ExceptionInInitializerError
at com.arcsoft.perfect365.MakeupApp.h(Unknown Source)
at com.arcsoft.perfect365.MakeupApp.onCreate(Unknown Source)
at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1001)
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4447)
at android.app.ActivityThread.access$1300(ActivityThread.java:145)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1298)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:5099)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:511)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:803)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:570)
at dalvik.system.NativeStart.main(Native Method)
Caused by: java.lang.UnsatisfiedLinkError: Couldn't load arcsoft_hairsalon from loader dalvik.system.PathClassLoader[dexPath=/data/app/com.arcsoft.perfect365-2.apk,libraryPath=/data/app-lib/com.arcsoft.perfect365-2]: findLibrary returned null
at java.lang.Runtime.loadLibrary(Runtime.java:365)
at java.lang.System.loadLibrary(System.java:535)
at com.meiren.FlawlessFace.FlawlessFaceLib.<clinit>(Unknown Source)
... 14 more
at com.arcsoft.perfect365.MakeupApp.h(Unknown Source)
at com.arcsoft.perfect365.MakeupApp.onCreate(Unknown Source)
at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1001)
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4447)
at android.app.ActivityThread.access$1300(ActivityThread.java:145)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1298)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:5099)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:511)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:803)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:570)
at dalvik.system.NativeStart.main(Native Method)
Caused by: java.lang.UnsatisfiedLinkError: Couldn't load arcsoft_hairsalon from loader dalvik.system.PathClassLoader[dexPath=/data/app/com.arcsoft.perfect365-2.apk,libraryPath=/data/app-lib/com.arcsoft.perfect365-2]: findLibrary returned null
at java.lang.Runtime.loadLibrary(Runtime.java:365)
at java.lang.System.loadLibrary(System.java:535)
at com.meiren.FlawlessFace.FlawlessFaceLib.<clinit>(Unknown Source)
... 14 more
sh...@gmail.com <sh...@gmail.com> #58
What can I fixed this issues!!!!!Pls!
al...@gmail.com <al...@gmail.com> #59
We received 1,264 crashes this week because of this bug.
I need an ETA for this fix.
I need an ETA for this fix.
jo...@gmail.com <jo...@gmail.com> #60
I have a similar issue. After installing an update with a new version of the sqlcipher native library. The native library has not been updated:
Caused by: java.lang.UnsatisfiedLinkError: Native method not found: net.sqlcipher.database.SQLiteDatabase.native_key:([C)V
at net.sqlcipher.database.SQLiteDatabase.native_key(Native Method)
at net.sqlcipher.database.SQLiteDatabase.<init>(SQLiteDatabase.java:1948)
at net.sqlcipher.database.SQLiteDatabase.openDatabase(SQLiteDatabase.java:875)
at net.sqlcipher.database.SQLiteDatabase.openOrCreateDatabase(SQLiteDatabase.java:907)
at net.sqlcipher.database.SQLiteOpenHelper.getWritableDatabase(SQLiteOpenHelper.java:132)
at net.sqlcipher.database.SQLiteOpenHelper.getWritableDatabase(SQLiteOpenHelper.java:99)
Caused by: java.lang.UnsatisfiedLinkError: Native method not found: net.sqlcipher.database.SQLiteDatabase.native_key:([C)V
at net.sqlcipher.database.SQLiteDatabase.native_key(Native Method)
at net.sqlcipher.database.SQLiteDatabase.<init>(SQLiteDatabase.java:1948)
at net.sqlcipher.database.SQLiteDatabase.openDatabase(SQLiteDatabase.java:875)
at net.sqlcipher.database.SQLiteDatabase.openOrCreateDatabase(SQLiteDatabase.java:907)
at net.sqlcipher.database.SQLiteOpenHelper.getWritableDatabase(SQLiteOpenHelper.java:132)
at net.sqlcipher.database.SQLiteOpenHelper.getWritableDatabase(SQLiteOpenHelper.java:99)
vi...@gmail.com <vi...@gmail.com> #61
Hi All
We do also see this similar issues reported by the customer for our application, but unfortunately we have not been able to reproduce with the devices we have.
If any one knows please share how can we reproduce the issue during upgrade where client app will not be able to load the native library instead throws the error and crashes.
Additionally, we are looking for the solution as well since the crash count for our app has increased to 1K in the google play.
regards
We do also see this similar issues reported by the customer for our application, but unfortunately we have not been able to reproduce with the devices we have.
If any one knows please share how can we reproduce the issue during upgrade where client app will not be able to load the native library instead throws the error and crashes.
Additionally, we are looking for the solution as well since the crash count for our app has increased to 1K in the google play.
regards
ju...@gmail.com <ju...@gmail.com> #62
This is still not working. Its so frustrating to be an android developer when everything is so broken.
[Deleted User] <[Deleted User]> #63
[Comment deleted]
te...@gmail.com <te...@gmail.com> #64
Please provide us support for this issue, this is killing our application simply because of our dependencies on native libraries.
We are encountering it on the following devices/OS:
Android 4.3 :63.6%
Android 4.2: 36.4%
Galaxy S3 (d2can)
Galaxy Tab3 8.0 (lt01wifi)
Xperia SP (C5306)
Xperia Z (C6616)
Xperia M (C1904)
ME173X (ME173X)
Thank you
We are encountering it on the following devices/OS:
Android 4.3 :63.6%
Android 4.2: 36.4%
Galaxy S3 (d2can)
Galaxy Tab3 8.0 (lt01wifi)
Xperia SP (C5306)
Xperia Z (C6616)
Xperia M (C1904)
ME173X (ME173X)
Thank you
jo...@gmail.com <jo...@gmail.com> #65
The only way to be sure that the native lib is loaded is to load yourself the lib with System.load()
[Deleted User] <[Deleted User]> #66
Same happens for me on Galaxy Note 8.0 (Android 4.2.2).
er...@gmail.com <er...@gmail.com> #67
I'm seeing this error as well and it is not related to installing the app through Google Play (.e., it happens when installing with ADB sometimes as well).
The closest I've been to reproduce it is to use an emulator where I fill up almost all of the internal storage and then try to install. The APK installs, but the .so file isn't extracted correctly.
The closest I've been to reproduce it is to use an emulator where I fill up almost all of the internal storage and then try to install. The APK installs, but the .so file isn't extracted correctly.
Description
Devices: Nexus and Xoom
Problem: System.loadLibrary() fails with:
STACK_TRACE=java.lang.UnsatisfiedLinkError: Couldn't load aeogg: findLibrary returned null
at java.lang.Runtime.loadLibrary(Runtime.java:365)
at java.lang.System.loadLibrary(System.java:535)
The library itself does not matter. They are binary identical to my previous releases of the app. Switching loadLibrary() to load another one first will just fail on the first library encountered.
On first installation of the app, it all runs fine. Installing the next version of the app without any changes to the native libraries will fail to install either from the market or directly from an .apk. This ONLY happens on 4.1.1, all upgrades of my other clients went fine, so this is definately a problem with Jelly Bean.
The problem can be worked-around by un-installing the .apk and then re-installing (from either market or .apk). Might be a bug in Jelly Bean's partial .apk upgrades?