-
Notifications
You must be signed in to change notification settings - Fork 45
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
Android Release build issue #9
Comments
Specifically, What went wrong: |
Grab a shot of your terminal with the full error message and paste that here please. Would need to ascertain it's something for me to help with or something strictly for the guys at Paystack! |
+1 |
The task Try to recompile doing the following:
|
I have indeed tried each of your recommendations and confirmed that the loginbtn.png is indeed there. Note, when I removed the react-native-paystack package and then set aapt2 to false, it was able to Successfully compile without any other changes, which is what led me to the conclusion that it was indeed something with the package that was causing the issues. |
So I can't reproduce your issue and hence may not be able to help further. It looks simple enough though, as it's just a case of RN asset compilation in release mode. You can try setting up a new RN project, sample App.js code is just fine to test (don't add your app logic or asset). Add the package, do the linking and just try to make a release mode and see if you can reproduce the issue on this separate build. |
Hi, So yea I just ended up recreating my package and it works fine, I was able to do a live payment with OTP and Pin. Many thanks for your work and effort amigo |
@aolowude What did you do last? |
how was this issue resolved @aolowude |
So I have debugged and pinpointed that in Release Mode, react native apps don't compile in release mode, they only work in debug mode.
I tested by removing all the Paystack code and uninstalling and it compiles fine into release mode, but when compiling to release, I had to
Please assist.
The text was updated successfully, but these errors were encountered: