-
Notifications
You must be signed in to change notification settings - Fork 935
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Building App with SDK 29 Crash on Android 10 #2927
Comments
@satyajiit The issue is specified clearly. Please look into the logs |
@codedsun I have gone through the logcat but couldn't find a correct clue to track the issue. |
@satyajiit Please look this Also please get this done as early as possible |
@codedsun The Quick Fix can be to downgrade the compileSDK to 28 . |
please mention what context issues.
…On Wed, Nov 20, 2019, 10:13 PM Satyajit Pradhan ***@***.***> wrote:
@codedsun <https://github.com/codedsun> The Quick Fix can be to downgrade
the compileSDK to 28 .
Trying to fix the issue with the Iconics is successful ,
But i seem to get more issues related to Context.
On SDK 29 , seems to have some behavior changes.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2927?email_source=notifications&email_token=AEYZISCRGX4DECRF7Y4PD6LQUVSM7A5CNFSM4JO36FA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEESUY4Y#issuecomment-556092531>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEYZISGR5Y5MJAEHVYW3QFLQUVSM7ANCNFSM4JO36FAQ>
.
|
@satyajiit Updates? |
@codedsun I am having my end terms/sem now 😟 . |
Please add |
@codedsun Some non-SDK access warnings are also there ,
Ref : https://developer.android.com/about/versions/10/non-sdk-q |
@iamareebjamal I need your help here, when I bumped the version of IconicsLibray to v3.2.5 (which is not the latest but we have used as its the latest for non-kotlin projects) But I am still getting the same crash on Android 10. Also, please look at this and guide us what is to be done ? |
Why are you not uprading to the latest version?
Every kotlin library can work with java, that's the point of kotlin Why won't this work? mikepenz/Android-Iconics#470 (comment) |
@iamareebjamal - We are not using IconicsContextWrapper, the crash is of InternalLayoutInflater
|
And how does it matter? Either the issue you linked is not related to the crash, or the fixes mentioned in it will work. How does it matter that we are not using IconicsContextWrapper, issue has to be fixed anyway |
Issue has to be fixed but you asked here why wont this work, it was the reply of that question. |
Why not use the latest version instead of trying to fix a buggy and outdated version? |
I did that but still facing some issues, will solve and send the PR |
@iamareebjamal I have upgrarded to the latest version but the app is still crashing on
|
@iamareebjamal - Also see the comment under release v4.0.0 https://github.com/mikepenz/Android-Iconics/releases They say:
|
@iamareebjamal - I have opened an issue on their issue tracker, I am getting error at inflating menu items in our app. |
Android says |
Describe the bug
Building the App with SDK Tools 29 and BuildTools 29.0.2 will not run on android 10 devices.
The official version of the app i.e "1.10.0" is also built with SDK 29 ,
Hence the app is crashing on all android 10 devices.
To Reproduce
Expected behavior
Should Run on Android 10 devices.
Logs
GIF Showing Crash of Debug Release using SDK 29
GIF Showing Crash of latest version App from PlayStore
Smartphone Info:
Additional context
The App runs fine on android versions < 10.
It seems to occur because of some outdated dependency libraries.
Since on android sdk 29, androidx has components been made mandatory ,
It might be that one of the library most probably Android-Iconics is causing the issue ( As checked from the logs ).
Currently the fast work-ground can be to use SDK 28 to build the project.
Would you like to work on the issue?
For fast solution I can create a PR to downgrade the sdk to 28 ,
Need your suggestions and reviews.
The text was updated successfully, but these errors were encountered: