Eduardo Speroni

@farfromrefug in Android, the launch event is called when the Activity has launched, not the Application. This would also mean that flavors would have to handle different events for android/ios...

on iOS, application is available from the start (before Application.run). On Android, it's available directly after Application.run (I've talked with @rigor789 and we'll most likely refactor it to make it...

On android 11- the launch event is called multiple times (open app, launch is called, use back button, exit is called, open app again, launch is called). The idea of...

This seems to be causing some confusion. Let me clarify it a bit: ```ts // main.ts console.log('Starting main.ts'); firebase() .messaging() .onMessage((remoteMessage) => { console.log('received firebaseMessage'); }); Application.on('launch', (args) => {...

On iOS you can initialize right away, I'm initializing after Application.run on Android (or in my case runNativeScriptApp). Soon you should be able to initialize anywhere on Android (once we...

@anarnoli there's no error there, that disconnect is the test runner disconnecting after a full run.

@anarnoli What do you mean? Why do you want it to remain connected? You can use `--env.stayOpen` so your app doesn't close after each run, you also need `singleRun: false`...

1. Add this to your webpack config in `webpack.chainWebpack` for the moment. (It seems we forgot to add it to the unit test runner V3, will fix tomorrow) ``` const...

This is a tricky thing to do because sometimes you want to resolve in a background thread. For example, if you're doing a heavy operation or using APIs that shouldn't...