<![CDATA[Sign in with Apple stopped working after upgrading to FusionAuth 1.69.0]]>After upgrading to FusionAuth 1.69.0, Sign in with Apple identity provider stopped working across all environments. The application was using an Apple identity provider configuration that was created prior to the upgrade. The 1.69.0 migration guide mentions potential issues with keys that were set up before upgrading.

What changed in 1.69.0 that could affect existing Apple identity provider configurations, and how can this be resolved?

]]>https://fusionauth.io/community/forum/topic/3240/sign-in-with-apple-stopped-working-after-upgrading-to-fusionauth-1-69-0RSS for NodeWed, 14 Oct 2026 02:09:33 GMTFri, 09 Oct 2026 13:33:06 GMT60<![CDATA[Reply to Sign in with Apple stopped working after upgrading to FusionAuth 1.69.0 on Fri, 09 Oct 2026 13:33:16 GMT]]>FusionAuth 1.69.0 introduced changes to how Apple identity provider keys are handled. If your Apple identity provider was configured before upgrading to 1.69.0, you may need to update the key configuration.

To resolve this issue:

  1. Review the 1.69.0 migration guide for specific details about Apple identity provider key changes
  2. Navigate to your Apple identity provider configuration in the FusionAuth admin UI
  3. Verify that the signing key is properly configured and valid
  4. If needed, re-import or reconfigure the Apple private key used for the identity provider
  5. Test the Sign in with Apple flow after making these changes

The migration guide contains detailed steps for addressing key-related issues introduced in this version.

]]>https://fusionauth.io/community/forum/post/8817https://fusionauth.io/community/forum/post/8817Fri, 09 Oct 2026 13:33:16 GMT