Brian Lenz

I used this patch to check `canScheduleExactAlarms()`: ``` diff --git a/android/src/main/java/com/dieam/reactnativepushnotification/modules/RNPushNotificationHelper.java b/android/src/main/java/com/dieam/reactnativepushnotification/modules/RNPushNotificationHelper.java index 248ff0825af89ce82e2c7346ef1edc104b06c91c..a228a63f1033fac9622148de79928fed90e26d95 100644 --- a/android/src/main/java/com/dieam/reactnativepushnotification/modules/RNPushNotificationHelper.java +++ b/android/src/main/java/com/dieam/reactnativepushnotification/modules/RNPushNotificationHelper.java @@ -170,6 +170,12 @@ public class RNPushNotificationHelper { if (pendingIntent ==...

I was running into similar issues here. I started playing around with the tests (which were working just fine) and adapted the test here for a scenario that is not...

See [my comment](https://github.com/neonexchange/neo-ico-template/pull/19#issuecomment-369768629) in #19 for why I believe the behavior of `transferFrom` should remain unchanged.

FYI, it looks like the Dependabot alert was updated, and this is no longer a security issue. The updated status shows that it's fixed in `7.0.36`: https://github.com/github/advisory-database/commit/df3034df6abfc28ab60a5a328cf502b0df65dbdb

We ran into this issue, too. [react-native-firebase](https://github.com/invertase/react-native-firebase) `15.x` requires `use_frameworks!`, per: https://rnfirebase.io/#altering-cocoapods-to-use-frameworks For us, the solution was to downgrade `react-native-firebase` to `14.x` (and disable `use_frameworks!`) until there is better support...

FWIW, it crashes if you run a `Release` build on the Simulator, too.

Since we are using Amplify CLI `9.1.0` for Amplify frontend builds in the console, I tried switching to the `9.1.0` CLI locally, and it has the same hanging issue, so...

@josefaidt, thanks for the response! My follow-ups: * The log is `2.2MB` and contains project-specific info we'd prefer not to post publicly. Is there some way to share it privately?...

@josefaidt, I don't know if this is related, but we noticed today that when we view the details of a backend environment in the Amplify console, the page "crashes" and...

@josefaidt, FYI, I successfully created a new `staging` environment yesterday. It's up and running without issue, as production continues to be. For whatever reason, the `dev` environment remains broken when...