WAI
Status Update
Comments
om...@gmail.com <om...@gmail.com> #2
Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:
Please provide sample project or apk to reproduce the issue.
Also mention the steps to be followed for reproducing the issue with the given sample project or apk.
Expected output
What is the expected output?
Current output
What is the current output?
logcat output
Seehttp://developer.android.com/tools/help/logcat.html . Copy and paste relevant sections of the logcat output into this issue.
Please provide sample project or apk to reproduce the issue.
Also mention the steps to be followed for reproducing the issue with the given sample project or apk.
Expected output
What is the expected output?
Current output
What is the current output?
logcat output
See
[Deleted User] <[Deleted User]> #3
Thanks for the response! Have a look at the expected.png and issue.png files attached to the original report. I also added code to reproduce the issue in the original report. You may also have a look at (and clone) this sample application, where I've also illustrated the problem in the README with an “expected” and “actual” image. https://github.com/sindrenm/bug-report-sample-androidx-128646026
[Deleted User] <[Deleted User]> #4
We have run the sample provided (in comment #3 ) in Q build and P build which are not similar to the screen shots provided expected.png and issue.png.
Please confirm if this is the issue. If not please provide the right sample code to reproduce the issue accordingly to what you experience.
Please confirm if this is the issue. If not please provide the right sample code to reproduce the issue accordingly to what you experience.
om...@gmail.com <om...@gmail.com> #5
Thanks for trying it out! Yeah, your screenshots also have the issue. As you can see, there's a lot of red background in your screenshot. That red background is the background color of the RecyclerView itself and should not be visible because that has a WRAP_CONTENT height and all of its children are fully opaque white.
The repo also contains a layout file with an item view that does not produce the problem (working_item_view.xml), and if you inflate that one instead in the adapter you will see that the background color that is shown as red in your screenshots will be blue. Blue is the background color of the root view (ConstraintLayout) which is full size in the activity and should thus be visible between the green view at the bottom and the RecyclerView.
The repo also contains a layout file with an item view that does not produce the problem (working_item_view.xml), and if you inflate that one instead in the adapter you will see that the background color that is shown as red in your screenshots will be blue. Blue is the background color of the root view (ConstraintLayout) which is full size in the activity and should thus be visible between the green view at the bottom and the RecyclerView.
wa...@gmail.com <wa...@gmail.com> #6
Assigning to AndroidX (Support Library) > Recyclerview. More details are here :
https://drive.google.com/open?id=10--sB0_WvGrHur_iiyBQM-8yzxvaYLHo (internal only link)
Description
- Steps to reproduce the problem (including sample code if appropriate).
- What happened.
- What you think the correct behavior should be.
Steps to reproduce:
(happens on Nexus One, doesn't happen on Droid)
In an Android project, create folders for both armeabi and armeabi-v7a.
Put one library in armeabi-v7a, and other libraries only in armeabi.
The scenario is that you have one "fat loaded" library that you compiled for both instruction sets, and other libraries that you compiled only for armeabi.
Then, use System.loadLibrary() to load a library from armeabi that you didn't compile for armeabi-v7a.
What happens:
When you try to load a library that is present only in armeabi, you get UnsatisfiedLinkError - it won't load it.
If you remove the one library in armeabi-v7a, it will load.
Correct behavior:
For EACH library, check if it exists in armeabi-v7a. If it does, load it. If not, check if it exists in armeabi. If it does, load it. If not, throw UnsatisfiedLinkError.
In any way, the existance of one particular library in armeabi-v7a shouldn't affect other libraries that have nothing to do with it.
Workaround:
Put ALL your libraries both in armeabi and armeabi-v7a. This could take a lot of space. In my case, the .APK has to grow from 3MB to 4.5MB because of the duplicate library.
Stack trace:
06-15 12:16:18.024: ERROR/app(2509): Caused by: java.lang.UnsatisfiedLinkError: Library some-library not found
06-15 12:16:18.024: ERROR/app(2509): at java.lang.Runtime.loadLibrary(Runtime.java:489)
06-15 12:16:18.024: ERROR/app(2509): at java.lang.System.loadLibrary(System.java:557)
06-15 12:16:18.024: ERROR/app(2509): at com.app.SomeClass.<clinit>(SomeClass.java:62)
06-15 12:16:18.024: ERROR/app(2509): ... 28 more