Closed annadanchenko closed 5 years ago
@jakubgs since you just had a stab at the ndk filter could you look at this? seems like https://github.com/facebook/react-native/issues/24261 could solve this
@yenda
Temporary Workaround: When I removed 64 bit ndk filters "arm64-v8a", "x86_64" from ndk abiFilters in defaultConfig block of buidl.gradle by provide only 32 bit support
How is that any help when we need 64 bit support to do a release starting from 1st of June?
apparently realm doesn't support 64 bits yet anyway https://github.com/realm/realm-js/issues/2282#issuecomment-498329160
According to this: https://github.com/facebook/react-native/issues/25060#issuecomment-497993541
Magical part of code saved my life. add this to app/build.gradle:
ndk { abiFilters "armeabi-v7a", "x86" }
But that's nonsense because we need arm64-v8a
to be compliant with the new Play Store requirements:
https://developer.android.com/distribute/best-practices/develop/64-bit
For the ARM architecture, the 32-bit libraries are located in armeabi-v7a. The 64-bit equivalent is arm64-v8a.
and:
the presence of armeabi-v7a and arm64-v8a libraries, which means the app supports 64-bit architectures.
So we can't just drop it, or we will be unable to release to the Play Store.
update on devices where issue can be reproduce and not:
Can reproduce issue
Can't reproduce issue:
Confirms that it is 64 bits phones
@jakubgs we can drop it until realm supports it, so I'll be watching their issue, it shouldn't take long
Okay, we can do that, but just to be clear, we won't be able to do Android releases until we undo the temporary fix: #8367
This happens to my Samsung S6 Edge, Android 7 as well.
Which branch of the upstream repo can I rebase my own development branches with so I can continue development?
@krisc you can try #8367 and tell us if it helped.
@krisc please try https://github.com/status-im/status-react/pull/8368 first
the first build, the others don't matter it's just stupid yarn doing too much
Description
Type: Bug
Summary: Can't launch app, see "Unfortunately, Status has stopped" popup instead. Installed Android nightly build from https://ci.status.im/job/status-react/job/nightly/1105/
Note that previous nightly https://ci.status.im/job/status-react/job/nightly/1104/ can be installed and launched fine. Assume that the issues is introduced by https://github.com/status-im/status-react/pull/8336
Expected behavior
app launched
Actual behavior
"Unfortunately, Status has stopped" popup
logcat contains
Reproduction
Additional Information
Logs
full logcat: cantstart.txt