Fixes for iOS and fully working with Android (including Oreo, Pie, Q)

[woffu]

• IOS, We fixed the issue with the RNBoundary.podspec
• Android, We fixed the issue with startService when the app is in background and correctly handling it using a startForegroundService with a binded notification.

[gate8team]

Any news on the delivery date for the fix?

[AlekseiSkrebkov]

When do you think this fix will be merged?

[johnou]

cc @eddieowens

[grubstarstar]

@eddieowens is this going to be merged or should I use @woffu's fork?

[mathiasmoeller]

Any news if this will be merged?

[mathiasmoeller]

@woffu Your fixes seem to work! Great stuff. But could you maybe give me an example on how to handle events when the app was killed? I add some boundaries, I attach EXIT and ENTER listeners. Everything works while the app is in foreground or in background. When I kill the app and leave the boundary, I can see in the React Native Debugger that the App is triggered. The console logs an onExit event from the boundary index.js file. But the listeners that I attached are not called. I guess the reason is that they were destroyed when the app was killed. I tried to attach the listeners again on App start in my index.js file (I guess that is the earliest time I can do something) but it did not work. Since you worked with this feature could you maybe give me an example on how you listened to ENTER/EXIT events when the app was killed? Help is very much appreciated!

[cladjules]

Hi @woffu , great work, thanks for the PR!

That PR has been open for months and there is no update, I need to do the same fix for iOS (work in the background), I have merged it in my own PR https://github.com/eddieowens/react-native-boundary/pull/56

I wonder if we should start maintaining that project in another github?