-
Notifications
You must be signed in to change notification settings - Fork 18
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
Callback for callProjectApi() doesn't get executed on native platforms #23
Comments
Hey @ljudbane |
Hey @ljudbane |
@snyuryev Thank you, i will check it out and report back if the issue is fixed for me. |
I did some testing on iOS simulator. First i updated libs to most recent versions:
First call in our app to project API is:
And in the log of simulator there are not any console.log outputs from callback function, nor from the catch block:
Then i click on a button in our app that launches another callProjectAPI:
And in the log i see the same error that was present before at the time of original issue:
Every subsequent callProjectApi will trigger the error. Only the first one won't. We plan to test on Android next, so i will report those findings later. |
I've also tested on Android and the code in callback function doesn't get executed. I don't see any error in logcat. |
@ljudbane Did you run |
@snyuryev Yes i did, multiple times. Sorry for the late reply. I will try to replicate the issue in one of your example apps. |
When we call callProjectApi() from ionic application to execute a command from Alan scripts, the callback doesn't get executed when running on Android or iOS device (or simulator). It does work when running in browser (ionic serve).
For example we call Alan's function
greetUser
from ionic:The callback function doesn't get called and those console logs don't ever get printed. Neither is there any caught exception. When testing on Android device we didn't see anything in the logs that would indicate what's the problem. But when running on iOS there is a log entry that could point to the problem:
The text was updated successfully, but these errors were encountered: