Post

Replies

Boosts

Views

Activity

Reply to APNs token auth suddenly returns InvalidProviderToken for active team-scoped APNs key
Update with Push Notifications Console tests: I also tested Apple’s Push Notifications Console directly for the selected app/topic app.terrasignal. Device Token Validator: Result: Valid Message: “Device Token is valid for sending Alert & Background push-type notifications in the Development environment.” Console Send test #1: Environment: Development apns-topic: app.terrasignal apns-push-type: alert apns-priority: High (10) apns-id: 7498ec76-6ca6-4bde-af33-75783e19478c apns-unique-id: 7e0d597a-704c-a6ad-6ad9-4401de6989c4 Result: no notification arrived on the device Delivery Log lookup for apns-unique-id returned “No notification found” Console Send test #2: Environment: Development apns-topic: app.terrasignal apns-push-type: alert apns-priority: High (10) Payload included sound: default apns-id: bc0b2541-5b5e-4071-8f0e-9e7bff83985e apns-unique-id: 38070820-6e03-1a25-e6ff-5d1d35946d34 Sent: Jun 02, 2026, 8:03:16.279 PM CST Result: no notification arrived on the device Delivery Log lookup for apns-unique-id returned “No notification found” On the iPhone, Settings → Notifications → TerraSignal shows: Allow Notifications ON Lock Screen ON Notification Center ON Banners ON Sounds ON Badges ON Separate but related: JSON Web Token Validator still reports: “Team Id in request does not match with Issuer (iss) in token” My server direct APNs HTTP/2 request returns HTTP 403 {"reason":"InvalidProviderToken"} At this point, Apple’s own Device Token Validator says the token is valid, but Apple’s own Send/Delivery Log path does not produce a device notification or delivery-log result, and provider JWT validation still reports a team/issuer mismatch. Can you inspect the APNs backend for app/topic app.terrasignal under Team ID 837F2XGDX? -Yes I am using chatgbt on highest settings. I have been an Apple fan boy and supporter since 2001 and since the colorful clamshell little laptops, I own the original iphone and original ipod still and damn, I admit at this moment, I am Disheartened that I am not getting any help, just from AI. Nearly 300 thread views and nadda. Is there a way to by you a beer or something?
Jun ’26
Reply to APNs token auth suddenly returns InvalidProviderToken for active team-scoped APNs key
Still at a loss of what to do. Claude 4.8 says Apple/Chatgbt 5.5 thinking points to this on Apple's side. I am hoping it is something simple. It could be something I did but I just don't know. I simply don't know what more I can do and so many hours I have put into this project to just be in limbo and getting nowhere. Do I delete my apple developer account and go down that road of starting over?
Jun ’26
Reply to APNs token auth suddenly returns InvalidProviderToken for active team-scoped APNs key
Thank you so much for your time!! — I tested both tools in the Push Notifications Console. Selected app/context: App/topic: app.terrasignal Console URL context appears to be: teams/837F2XGDX/app/app.terrasignal Device Token Validator: Result: Valid Message shown: “Device Token is valid for sending Alert & Background push-type notifications in the Development environment.” This was the current sandbox/development token generated by the app and registered with my server. JSON Web Token Validator: Result: Failed Error shown: “Team Id in request does not match with Issuer (iss) in token” The JWT was generated on my VPS using the active APNs key HNW7XPK2H3 and Team ID 837F2XGDX. JWT header: { "alg": "ES256", "kid": "HNW7XPK2H3" } JWT payload: { "iss": "837F2XGDX", "iat": 1780268873 } I did not post the full JWT or private key publicly. This seems to narrow the issue: The device token validates successfully for Development. The app/topic selected in Push Notifications Console is app.terrasignal. The visible console team context appears to be 837F2XGDX. The JWT issuer is also 837F2XGDX. But Apple’s JWT Validator still reports a Team ID / issuer mismatch. This matches my server-side APNs result: HTTP 403 {"reason":"InvalidProviderToken"} Can you please check whether the APNs backend association between app/topic app.terrasignal, Team ID 837F2XGDX, and APNs key HNW7XPK2H3 is correct? If you still need a failed APNs request timestamp/apns-id, I can send another direct HTTP/2 request and provide the exact UTC time and any response headers returned.
May ’26
Reply to APNs token auth suddenly returns InvalidProviderToken for active team-scoped APNs key
I can provide redacted screenshots of: Xcode Signing & Capabilities showing Push Notifications enabled Apple Developer portal Key Details Bundle ID Push Notifications capability APNs direct HTTP/2 smoke test output Server APNs diagnostics showing InvalidProviderToken I will not post full device tokens, .p8 private key contents, debug secrets, or private server files publicly.
May ’26
Reply to APNs token auth suddenly returns InvalidProviderToken for active team-scoped APNs key
Update with Push Notifications Console tests: I also tested Apple’s Push Notifications Console directly for the selected app/topic app.terrasignal. Device Token Validator: Result: Valid Message: “Device Token is valid for sending Alert & Background push-type notifications in the Development environment.” Console Send test #1: Environment: Development apns-topic: app.terrasignal apns-push-type: alert apns-priority: High (10) apns-id: 7498ec76-6ca6-4bde-af33-75783e19478c apns-unique-id: 7e0d597a-704c-a6ad-6ad9-4401de6989c4 Result: no notification arrived on the device Delivery Log lookup for apns-unique-id returned “No notification found” Console Send test #2: Environment: Development apns-topic: app.terrasignal apns-push-type: alert apns-priority: High (10) Payload included sound: default apns-id: bc0b2541-5b5e-4071-8f0e-9e7bff83985e apns-unique-id: 38070820-6e03-1a25-e6ff-5d1d35946d34 Sent: Jun 02, 2026, 8:03:16.279 PM CST Result: no notification arrived on the device Delivery Log lookup for apns-unique-id returned “No notification found” On the iPhone, Settings → Notifications → TerraSignal shows: Allow Notifications ON Lock Screen ON Notification Center ON Banners ON Sounds ON Badges ON Separate but related: JSON Web Token Validator still reports: “Team Id in request does not match with Issuer (iss) in token” My server direct APNs HTTP/2 request returns HTTP 403 {"reason":"InvalidProviderToken"} At this point, Apple’s own Device Token Validator says the token is valid, but Apple’s own Send/Delivery Log path does not produce a device notification or delivery-log result, and provider JWT validation still reports a team/issuer mismatch. Can you inspect the APNs backend for app/topic app.terrasignal under Team ID 837F2XGDX? -Yes I am using chatgbt on highest settings. I have been an Apple fan boy and supporter since 2001 and since the colorful clamshell little laptops, I own the original iphone and original ipod still and damn, I admit at this moment, I am Disheartened that I am not getting any help, just from AI. Nearly 300 thread views and nadda. Is there a way to by you a beer or something?
Replies
Boosts
Views
Activity
Jun ’26
Reply to APNs token auth suddenly returns InvalidProviderToken for active team-scoped APNs key
Still at a loss of what to do. Claude 4.8 says Apple/Chatgbt 5.5 thinking points to this on Apple's side. I am hoping it is something simple. It could be something I did but I just don't know. I simply don't know what more I can do and so many hours I have put into this project to just be in limbo and getting nowhere. Do I delete my apple developer account and go down that road of starting over?
Replies
Boosts
Views
Activity
Jun ’26
Reply to APNs token auth suddenly returns InvalidProviderToken for active team-scoped APNs key
Thank you so much for your time!! — I tested both tools in the Push Notifications Console. Selected app/context: App/topic: app.terrasignal Console URL context appears to be: teams/837F2XGDX/app/app.terrasignal Device Token Validator: Result: Valid Message shown: “Device Token is valid for sending Alert & Background push-type notifications in the Development environment.” This was the current sandbox/development token generated by the app and registered with my server. JSON Web Token Validator: Result: Failed Error shown: “Team Id in request does not match with Issuer (iss) in token” The JWT was generated on my VPS using the active APNs key HNW7XPK2H3 and Team ID 837F2XGDX. JWT header: { "alg": "ES256", "kid": "HNW7XPK2H3" } JWT payload: { "iss": "837F2XGDX", "iat": 1780268873 } I did not post the full JWT or private key publicly. This seems to narrow the issue: The device token validates successfully for Development. The app/topic selected in Push Notifications Console is app.terrasignal. The visible console team context appears to be 837F2XGDX. The JWT issuer is also 837F2XGDX. But Apple’s JWT Validator still reports a Team ID / issuer mismatch. This matches my server-side APNs result: HTTP 403 {"reason":"InvalidProviderToken"} Can you please check whether the APNs backend association between app/topic app.terrasignal, Team ID 837F2XGDX, and APNs key HNW7XPK2H3 is correct? If you still need a failed APNs request timestamp/apns-id, I can send another direct HTTP/2 request and provide the exact UTC time and any response headers returned.
Replies
Boosts
Views
Activity
May ’26
Reply to APNs token auth suddenly returns InvalidProviderToken for active team-scoped APNs key
with those brilliant minds here. Been stuck on this now 4 days and glad only testflight and not live. Any help/direction is welcome. I spent so many hours on this project and now to have no alerts arrive on the phones is disheartening. Thank you for your time and help in advance !
Replies
Boosts
Views
Activity
May ’26
Reply to APNs token auth suddenly returns InvalidProviderToken for active team-scoped APNs key
I can provide redacted screenshots of: Xcode Signing & Capabilities showing Push Notifications enabled Apple Developer portal Key Details Bundle ID Push Notifications capability APNs direct HTTP/2 smoke test output Server APNs diagnostics showing InvalidProviderToken I will not post full device tokens, .p8 private key contents, debug secrets, or private server files publicly.
Replies
Boosts
Views
Activity
May ’26