React-native-apple-authentication: identityToken sometimes null

[kp654321]

Probably not an issue with this library but wondering what kind of situation could cause the identityToken to be null when performRequest() succeeds?

We're seeing it returned as null around 50% of the time while authorizationCode, nonce and user have values.

• "react-native": "0.61.4",
• "@invertase/react-native-apple-authentication": "^2.0.2",
• iOS 13.3.1 and upwards

[mikehardy]

I've not noticed this (not to say it is not happening!) personally, so I have no special insight. I'm usually the only responder here though, I suggest asking on stackoverflow or perhaps there are some lurkers here that have seen this and could respond...

[bobinrinder]

We're experiencing it too, we haven't made updates to the app in days and just today it started flooding in out of nowhere, zero occurrences before... 😱

[bennom]

Same for us. But this doesn't seem to be related to this library in particular. We are using this library (version 2.1.0, react native version 0.63.4) on our mobile apps, but our web platform is having the same issue: "Invalid token specified". On web we are using the SDK from here appleid.cdn-apple.com/appleauth/static/jsapi/appleid/1/en_US/appleid.auth.js.

Yet we cannot give more detailed information, sadly.

[rajtejani]

I'm also experiencing this isssue.

[DIGITALSQUAD]

Same here.
I looked up my server's log, and found that some users succeed but some users failed.

I found an apple developers thread about this issue.
This might be a problem with the Apple servers and some users says that already resolved and some says not yet.
I tried on my server with my apple id and succeeded, but not sure already resolved for other users.

[kp654321]

@DIGITALSQUAD
Thanks for sharing this issue. It seems to be the relevant one.

I would mention that for us, we do not see some users failing and others succeeding. It's more like a lottery where we can get a token for a user 10 seconds after a previous auth request for the same user returns an object without a token.

[mikehardy]

Given this module is actually quite simple in it's Objective-C code - just wrapping the platform API and that's effectively it - with no release here, this should be an upstream issue so I am not surprised at @DIGITALSQUAD 's apple thread reference and was in fact expecting that.

Unfortunately I think the actual resolution here is "wait impatiently while Apple fixes it"

[bobinrinder]

FYI: For us it seems to have resolved itself with no changes.

[mikehardy]

Thanks for the report - I'm going to close this since I think it wasn't actionable here either way and is (very thankfully) apparently resolved.

The joy of distributed systems, especially when part of it is not in your control at all :-)