Local notifications work until standalone ios builds in testflight
See original GitHub issue🐛 Bug Report
Environment
Expo CLI 2.14.0 environment info:
System:
OS: macOS 10.14.4
Shell: 5.0.3 - /usr/local/bin/bash
Binaries:
Node: 10.15.3 - ~/.nvm/versions/node/v10.15.3/bin/node
Yarn: 1.15.2 - ~/.nvm/versions/node/v10.15.3/bin/yarn
npm: 6.9.0 - ~/.nvm/versions/node/v10.15.3/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
IDEs:
Xcode: 10.2/10E125 - /usr/bin/xcodebuild
npmPackages:
expo: ^32.0.0 => 32.0.1
react: ^16.5.0 => 16.5.0
react-native: https://github.com/expo/react-native/archive/sdk-32.0.0.tar.gz => 0.57.1
react-navigation: ^2.18.2 => 2.18.3
npmGlobalPackages:
expo-cli: 2.14.0
This app is being built for ios with expo build:ios --clear-push-cert
, with both testing and production certs setup and added to apple developer account for this app.
Steps to Reproduce
- Create a standard expo app
- Add a local notification (say 10 seconds in the future) like this
- Test app locally with
expo start
and expo client on device by viewing screen that sets notification, kill app (long swipe on iPhone X) and wait for ten seconds - Build standalone binary with
expo build:ios --clear-push-cert
- Be sure to provision keys through expo, but also setup certificates for Apple Developer portal and xcode
- Upload to TestFlight
- Run local native TestFlight application, repeat above exercise (load screen that sets notification, kill app, wait ten seconds
Expected Behavior
I expected the local native app to be able to fire the notification with the app in the background, just like when running through expo client.
Actual Behavior
When I follow the exact same process as from using expo client, the notification never happens. I checked in the TestFlight app to be sure notifications were enabled (true), but no luck. The rest of the app works exactly as intended.
Reproducible Demo
I know this is all based on once standalone binaries are built, which is why I didn’t just create a snack. Please let me know if there’s anything I can do to demonstrate, or provide more helpful information to figure this out.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:27 (7 by maintainers)
Ahh I got you - thanks for clarifying. I’ll give that a shot and report back.
Pretty sure that is what fixed it for me!
For total rookies to react AND react native (such as myself), sometimes it has to be painfully, mind-numbingly spelled out:
Step 2 was where the wheels fell off for me, thanks for updating the docs!