push notifications broken after another dev built the app locally with his expo account

Expo CLI 3.21.5 environment info: System: OS: macOS 10.15.4 Shell: 3.2.57 - /bin/bash Binaries: Node: 10.20.1 - ~/.nvm/versions/node/v10.20.1/bin/node Yarn: 1.22.4 - ~/.yarn/bin/yarn npm: 6.14.4 - ~/.nvm/versions/node/v10.20.1/bin/npm Watchman: 4.9.0 - /usr/local/bin/watchman IDEs: Android Studio: 3.6 AI-192.7142.36.36.6308749 Xcode: 11.5/11E608c - /usr/bin/xcodebuild npmPackages: expo: ^35.0.0 => 35.0.0 react: 16.8.3 => 16.8.3 react-native: https://github.com/expo/react-native/archive/sdk-35.0.0.tar.gz => 0.59.8 react-navigation: ^3.0.7 => 3.0.9 npmGlobalPackages: expo-cli: 3.21.5

The goal is to get push notifications working again in the app people already have installed.

I have a working published app. The push notifications were working fine yesterday. We had a new developer that needed to build a local archive for testing on a connected device with Xcode. He was using his own Expo account.

He built the app, and a new “Expo Push Notifications Key” was added to the developer portal. It took us a while to notice that all of the iOS push notifications had stopped. Android is still working fine. I can send push notifications to Android from Push Notification Tool — Expo but iOS pushTokens no longer work.

I removed his “Expo Push Notifications Key” leaving just mine. It’s been hours and nothing has changed. I’m worried about trying something else I can’t undo.

Is there something non-destructive I can try? Worst case is I’ll have to put out a new build with a new key.

I am getting this back from the receipts:

         "message":"The Apple Push Notification service failed to send the notification (reason: InvalidProviderToken, status code: 403). Read Apple's docs about \"Communicating with APNs\" to learn what this error means.",


From Android pushTokens I get "status":"ok"

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.