Cristiano Coelho

@TimMun interesting. Did you only fix it for iOS? Because I saw the issue happening on Android as well, and so far, only building an exact thumbnail image of the...

I see, any chance you can push that change as a pull request? I might tackle the android issue myself but I'm curious what was the actual fix for IOS.

Alright, wish I could get some more ideas. Guess that it is still a good idea to use a resized image as I did so a large image is not...

I've faced this issue as well. In my use case, it is related to `UniqueTogetherValidator`. The validator makes all fields required by default, which is not 100% correct. What if...

I'm pretty much using the example code, but `onNotification` doesn't fire if the app was closed (terminated), but then re-opened from the notification tap event: ``` PushNotification.configure({ // (optional) Called...

This is for both Android and iOS, and only for local notifications (not using remote). Calling `PushNotification.popInitialNotification` does seem to return the tapped notification though.

Just to be sure: if you completely kill the app (swipe it out) while the notification is still visible, then tap the notification, the app opens, `onNotification` is called for...

Release mode may solve it for iOS, but what about Android? So far the only work around that worked for me was to use `PushNotification.popInitialNotification` on a mount event.

Main activity is clean, and no custom splash screen (we are just using a background image) ``` public class MainActivity extends ReactActivity { /** * Returns the name of the...

@MarcoScabbiolo while you are at it, you may want to consider also removing some of the deprecated API calls. More specifically, `captureStillImageAsynchronouslyFromConnection` is deprecated, and so most of the classes...