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
Release Mode Issue #85
Comments
How you trying to charge the card |
Yes I was. |
Are you using the server implementation or the local implementation
…On Tue, 12 Jan 2021 at 13:25, Adewale Soetan ***@***.***> wrote:
How you trying to charge the card
Yes I was.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#85 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANAEHQXL4AGENTI6URPYFFTSZQ5VJANCNFSM4V3YWDAQ>
.
|
Not sure, can you please expatiate.... |
For firstly the error you got may be due to the fact a variable was unassigned or is null. For me my implementation of the plug-in on iOS works fine, doesn't seem to have any issue on both the emulator the physical device. A really doubt that it could go wrong on test flight. I would have checked it out but my membership expired and I'm yet to pay this year. Where exactly did you get this error! |
The variable is assigned as it works well on the emulator from cradle to grave i.e payment successful and feedback token received etc. |
You could check Have you tried running |
My Implementation on both iOS and Android Works fine in release! |
Thanks a lot. I finally found the problem, the variable was referencing a wrong key. It’s working now. Thanks a lot for all the help. |
Good day,
I’m currently having an error testing the implementation of the PayStack Flutter SDK on my mobile app.
It appears to work on the Emulator on Debug Mode but when on a Physical Device on Release Mode, while testing on TestFlight, I get the following error :
NoSuchMethodError: The getter 'length' was called on null.
Receiver: null
Tried Calling: length
TRY ANOTHER CARD
START OVER WITH SAME CARD
The text was updated successfully, but these errors were encountered: