You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Android: provider keys now actually save. The on-device server only accepted the old POST shape, while the bundled client saves with PUT {name, value, expiresAt} and reads the expiry via GET /api/keys?name=.... The app reported a successful save and stored nothing, so chats failed with the missing-key error. The full contract is implemented now - save with expiry, expiry lookup for the dialog, revoke one and revoke all - and chat requests extract the inner apiKey from the JSON object the Set Key dialog writes for custom endpoints.
Settings -> Provider Keys now shows the stored key's expiry, and the revoke button works.
Android
versionCode 7 / versionName 1.0.6, signed with the same release key as prior versions.
Desktop
Windows installer and portable builds; no functional changes from 1.0.5.