Release Notes

6 October 2026: coordinated SDK and WebView logout

Current integration baseline: gofa_firebase 1.0.19, gofa_core 1.1.6, gofa_webview 2.1.5, gofa_lessons 1.2.12, gofa_pose 2.2.19 and gofa_rehab 0.1.6.

• AuthManager.signOut() also blocks SDK-managed WebViews and waits for confirmation that their GOFA web sessions have signed out.
• Cleanup includes sessions left by closed SDK views. Unrelated browser data is not cleared. Failed cleanup is reported and protected views stay blocked.
• Host applications still handle their navigation, local member session and backend-session invalidation. Host-created WebViews require host integration.
• Requires the updated GOFA web logout bridge. See the authentication and logout examples.

6 October 2026: unified Challenge, Lessons and WebView sign-in

Previous integration baseline: gofa_firebase 1.0.18, gofa_core 1.1.5, gofa_webview 2.1.4, gofa_lessons 1.2.11, gofa_pose 2.2.18 and gofa_rehab 0.1.5.

• Challenge (gofa_pose), Lessons and WebView use the same customTokenProvider and share the member session internally.
• Challenge can initialize first or run alone. No manual Firebase-app handoff or fallback-account configuration is needed in member mode.
• Initialization rejects mixed member, tenant or environment settings and cannot automatically resume a logged-out session.
• Use the current authentication and logout examples.

The entries below describe earlier releases and are superseded by this baseline for new member-sign-in integrations.

6 October 2026: member session logout and Pose continuity

Published package baseline: gofa_firebase 1.0.17, gofa_core 1.1.4, gofa_webview 2.1.3, gofa_lessons 1.2.10, gofa_pose 2.2.17 and gofa_rehab 0.1.4.

• AuthManager.signOut() blocks re-login from pending requests and SDK listeners.
• WebView does not return a cached custom token after coordinated logout.
• Pose accepts the authenticated Firebase app and preserves the current member.
• High-level dependency minimums include the new session handling.
• See authentication and logout.

For package version compatibility and migration support, contact GOFA. Read SDK authentication for member sign-in through your backend.

2026-10-06

• gofa_pose 2.2.16 preserves an authenticated member during initialization and accepts the existing Firebase app. Backend-token integrations set isLoginDefaultFirebaseAuthAccount: false.
• Use gofa_lessons 1.2.9, gofa_webview 2.1.2, gofa_core 1.1.3 and gofa_firebase 1.0.16 for the corrected concurrent sign-in dependency chain.
• The backend member sign-in API documents the direct client ID/secret flow and optional scoped ClientToken.

2026-09-29

Server-provided member sign-in

The published packages support receiving a fresh Firebase custom token from the integrator's authenticated backend for member sign-in:

• gofa_firebase 1.0.15
• gofa_core 1.1.2
• gofa_lessons 1.2.8
• gofa_webview 2.1.1
• gofa_pose 2.2.14
• gofa_rehab 0.1.2

The GOFA server endpoint for this flow is being rolled out separately. Contact GOFA to plan the integration and migration of an existing app.

2026-04-13

GOFA SDK 3.13.2+113

This release updated gofa_firebase to 1.0.13 and gofa_webview to 1.2.3. Contact GOFA for version-specific authentication and identity guidance for an existing app.