We found our problem regarding the sandbox login error.
Seems like the account was associated to an AppleId that was invalid.
After logging out of the Apple ID account (using the System Settings window), we were able to log back into the sandbox account using the AppStore -> Settings option
martin_bwl
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
From
Montréal, QC, Canada
Post
Replies
Boosts
Views
Activity
Same thing here.
Also all sandbox subscriptions using those testers account are failing...
Hello @boulzz;
We are seeing the same issue here even when forcing the TLS connection to be V1.2.
Any luck into solving this?
Thanks
Can you post the details (redacted from private info) of your JWT.
You should not have to supply the public key. It is already stored within Apple's server and referenced via the "kid" in the header.
You can try manually generating a signed token with proper parameters and keys here and see if the signature validates.
https://token.dev/
We are having the same issue on our side with our server properly accepting TLS V1.2 connections.
However validating the TEST notification, the response was a "firstSendAttemptResult": "TLS_ISSUE".
Here's the CURL information to our server (domain redacted).
* Connected to ***.*** (***.***.***.xxxx) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/ssl/cert.pem
* CApath: none
* (304) (OUT), TLS handshake, Client hello (1):
* (304) (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN, server did not agree to a protocol
* Server certificate:
* subject: CN=xxxxxxx
* start date: Feb 28 00:00:00 2023 GMT
* expire date: Feb 28 23:59:59 2024 GMT
* subjectAltName: host "xxxx" matched cert's "***"
* issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA
* SSL certificate verify ok.
> GET / HTTP/1.1
Can you help us clear that issue? Thanks
Reported also as FB10684500
Can Big Sur Beta be installed on an external drive ? Seems the installer is skipping the destination selection option.
Yes both the Widget and the macOS app would be in the same team.
However that app data to be surfaced within the widget is not contained in a file but in a SQLite database.
So I understand correctly, I would have to create an AppExtension of type Action that would perform the proper data retrieval request on the shared database file.
Then the widget could leverage that App Extension to extract retrieved data and have those displayed in the Widget UI.
Let me know if solution path makes sense. Thanks for your reply.
Did you get a solution for this problem ?I'm just experiencing the same issue with the newly installed XCode 11.2.1.Thanks
Tried to reinitialize CocoaPods (clean and reinstall) and still have the same issue. Any other suggestions ? I'm evaluating a complete clean re-install of XCode...