jahaskell53
commented
2 months ago Having the same issue.
Open sushilbansal opened 2 months ago
jahaskell53
commented
2 months ago Having the same issue.
tolegenovbt
commented
2 months ago same
jahaskell53
commented
2 months ago @brentvatne Any updates on this? Notifications aren't deep linking and our app is already in the App Store.
jahaskell53
commented
2 months ago To clarify, I think the Expo Snack shows this with a scheduled notification; I am also having issues push notifications. It has been 3 weeks since this issue was opened, any help would be much appreciated please!
@tsapeta @EvanBacon @lukmccall @amandeepmittal
AnjalaD
commented
1 month ago Same issue
bmpickford
commented
1 month ago Might not be applicable to everyone but I was having this issue while the app was in a background state and found is was due to having a separate activity for the launcher. Solved by passing through the intent bundle from the launch activity to our main activity.
Relevant issue comment here: https://github.com/invertase/react-native-firebase/issues/3469#issuecomment-614990736
Minimal reproducible example
https://snack.expo.dev/@sushil_qeeper/push-notifications
What platform(s) does this occur on?
iOS
Where did you reproduce the issue?
in a development build
Summary
1) Followed the instructions to setup notifications or just open the snack. 2) Click on send the notification button 3) a notification will show up on the actual device; click on that notification Expected behavior:
Environment
expo-env-info 1.2.0 environment info: System: OS: macOS 14.4 Shell: 3.6.1 - /opt/homebrew/bin/fish Binaries: Node: 22.4.1 - /opt/homebrew/bin/node Yarn: 1.22.22 - /opt/homebrew/bin/yarn npm: 10.8.1 - /opt/homebrew/bin/npm Watchman: 2024.07.15.00 - /opt/homebrew/bin/watchman Managers: CocoaPods: 1.14.3 - /opt/homebrew/bin/pod SDKs: iOS SDK: Platforms: DriverKit 23.2, iOS 17.2, macOS 14.2, tvOS 17.2, visionOS 1.0, watchOS 10.2 Android SDK: API Levels: 29, 30, 31, 32, 33, 34 Build Tools: 30.0.2, 33.0.0, 34.0.0 System Images: android-29 | Intel x86 Atom, android-29 | Intel x86 Atom_64, android-29 | Google APIs Intel x86 Atom_64, android-29 | Google Play Intel x86 Atom, android-29 | Google Play Intel x86 Atom_64, android-32 | Google APIs ARM 64 v8a, android-34 | ARM 64 v8a, android-34 | Intel x86_64 Atom IDEs: Android Studio: 2024.1 AI-241.18034.62.2411.12071903 Xcode: 15.2/15C500b - /usr/bin/xcodebuild npmPackages: expo: ~51.0.28 => 51.0.31 expo-router: ~3.5.23 => 3.5.23 react: 18.2.0 => 18.2.0 react-dom: 18.2.0 => 18.2.0 react-native: 0.74.5 => 0.74.5 react-native-web: ~0.19.10 => 0.19.12 npmGlobalPackages: eas-cli: 11.0.3 Expo Workflow: bare
Expo Doctor Diagnostics
he name in your package.json is set to "expo-notifications", which conflicts with a dependency of the same name.
This project contains native project folders but also has native configuration properties in app.json, indicating it is configured to use Prebuild. When the android/ios folders are present, EAS Build will not sync the following properties: orientation, icon, scheme, userInterfaceStyle, splash, ios, android, plugins.
Advice: Add '/android' and '/ios' to your .gitignore file if you intend to use CNG / Prebuild. Learn more: https://docs.expo.dev/workflow/prebuild/#usage-with-eas-build
(node:70924) [DEP0040] DeprecationWarning: The
punycodemodule is deprecated. Please use a userland alternative instead. (Usenode --trace-deprecation ...to show where the warning was created) The following packages should be updated for best compatibility with the installed expo version: expo-font@12.0.9 - expected version: ~12.0.10 expo-dev-client@4.0.25 - expected version: ~4.0.26 Your project may not work correctly until you install the expected versions of the packages. Found outdated dependencies Advice: Use 'npx expo install --check' to review and upgrade your dependencies.