What problem does this solve, or what need does it fill?
The current Github Actions setup doesn't actually run Android and iOS applications on the iOS Simulator and Android Emulator. So it's hard to tell if the built application works as expected.
What solution would you like?
We can add two extra steps for Android and iOS build Actions: run Android Emulator and run iOS Simulator. Then we can run the crossbundle run command, read logs and find a specific log that we print from the Application example/test.
What alternative(s) have you considered?
I don't think anything else will be as bulletproof as running an actual Emulator or Simulator to test the correct work of application, but if someone knows a better solution - please refer to it in the comments on this issue. Also, to test Github Actions locally: use act.
What problem does this solve, or what need does it fill?
The current Github Actions setup doesn't actually run Android and iOS applications on the iOS Simulator and Android Emulator. So it's hard to tell if the built application works as expected.
What solution would you like?
We can add two extra steps for Android and iOS build Actions: run Android Emulator and run iOS Simulator. Then we can run the
crossbundle runcommand, read logs and find a specific log that we print from the Application example/test.What alternative(s) have you considered?
I don't think anything else will be as bulletproof as running an actual Emulator or Simulator to test the correct work of application, but if someone knows a better solution - please refer to it in the comments on this issue. Also, to test Github Actions locally: use act.