Joe Bernard

I found the issue. On line 466, make the following change: skipUpdateToHash = true; It was previously set to false. This will prevent EasyTabs from reloading after a hash change.

Also note that this issue only occurs when cache = false and updateHash = true. All your demos seem to be cached, which is why they don't display the error.

@JangoSteve I committed 078b63f which should resolve this issue. See comments for more details. I haven't fully tested this yet, so it may act funky with other cache / updateHash...

@prashantm8 No I was never able to find a good solution for this. Please post if you discover one.

I didn't attempt an implementation but we could definitely use it.

I've been testing with @mskri update and lgtm. Can we get this merged, please?

I noticed that `completionHandler()` was removed from the instructions in the readme recently: https://github.com/react-native-push-notification-ios/push-notification-ios/pull/207/files#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5L119 Are you calling `completionHandler()` there? Perhaps this is related to your issue.

Could it be that APNS is throttling your notifications when you start sending multiple manually? Maybe Apple is delaying them and they are reaching your device late. Do you see...

I don't even see `finish` being called in the example app. Very confused how this is implemented. https://github.com/react-native-push-notification/ios/blob/master/example/App.js

Can we get this one reviewed? Having time-sensitive notifications is an important feature.