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
"message": "[FAL] Add support for limited-use tokens (#7285)\n\nPer [b/440338679](https://b.corp.google.com/issues/440338679),\n\nThis adds support for the `useLimitedUseAppCheckTokens` parameter to the\n`getInstance` constructor and the `.ai` helper method.\n\nTo help assist this process, I've also update the\n`FirebaseAIMultiResourceComponent` to use a hashed data class containing\nall the unique data of each `getInstance`. Previously, it only tracked\ninstances by the location. Now, it tracks instances by the location,\nbackend, and the value of `useLimitedUseAppCheckTokens`. In all\npracticality, this is unlikely to get much usage, but it helps avoid any\npotential edge-case issues where customers expect different instances.\n\nDocumentation is present for the added changes, as well as a changelog\nentry. These both match what we did on the iCore side, but feel free to\nadjust as needed. Furthermore, the `api.txt` file has been updated with\nthe corresponding changes.",
"message": "[AI] Improve refdocs (#7282)\n\nThe improvements include:\n\n- Link directly to the list of supported models in the documentation.\n- Fix rendering issues with numbers being translated as numbered lists\n- Link to firebase documentation instead of vertex documentation when\ncorresponding.",
"message": "[AI] Add support for thinkingSummaries and thoughtSignatures (#7272)\n\nAdded support for returning [thought\nsummaries](https://ai.google.dev/gemini-api/docs/thinking#summaries)\nwhen using thinking-compatible models.\n\nAdditionally, it adds support for automatic handling of\n`thoughtSignatures`.\n\n---------\n\nCo-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>",
"message": "[AI] Correctly handle empty candidates in the accessors (#7270)\n\nBefore, if a response had no candidates, accessors would throw an\nexception when used instead of handle the case elegantly. Now they\neither return an empty list, for collections, or null, for string.\n\nThe test file is added in\nhttps://github.com/FirebaseExtended/vertexai-sdk-test-data/pull/48",
"message": "[Ai] Expose `APINotConfiguredException` in the public API (#7259)\n\nThe exception was added in #7233 but was mistakenly marked as internal.",
"message": "Added dilation parameter to generateMaskAndPadForOutpainting (#7260)\n\nThe dilation parameter gets passed through to the mask, and is optional.\n\nEnded up doing manual overloading to preserve binary compatibility.\n\n---------\n\nCo-authored-by: David Motsonashvili <[email protected]>",
"message": "Add NotConfiguredException with a better error message than provided by the server. (#7233)\n\nThe previous error text \"genai config not found\" is ambiguous and as a\ngeneric ServerException did not provide documentation for resolutions.",
"message": "Temporarily remove CHANGELOG entry (#7228)\n\nThe backend won't be published until sometime next week, removing this\nuntil it's ready. No changes to the code are necessary as there are no\npublic API changes and it'll still hit a runtime error.",
"message": "[Infra] Improve datastore support (#7277)\n\nBump the dependency to version 1.1.7 to include the mitigation\nintroduced in\n\nhttps://developer.android.com/jetpack/androidx/releases/datastore#1.1.5\n\nAdditionally, a corruption handler has been added to the\n`JavaDataStorage` class.\n\nInclude `firebase-sessions` changelog entry so it's released.\n\n---------\n\nCo-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>",
"message": "[Infra] Improve datastore support (#7277)\n\nBump the dependency to version 1.1.7 to include the mitigation\nintroduced in\n\nhttps://developer.android.com/jetpack/androidx/releases/datastore#1.1.5\n\nAdditionally, a corruption handler has been added to the\n`JavaDataStorage` class.\n\nInclude `firebase-sessions` changelog entry so it's released.\n\n---------\n\nCo-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>",
"message": "[Infra] Improve datastore support (#7277)\n\nBump the dependency to version 1.1.7 to include the mitigation\nintroduced in\n\nhttps://developer.android.com/jetpack/androidx/releases/datastore#1.1.5\n\nAdditionally, a corruption handler has been added to the\n`JavaDataStorage` class.\n\nInclude `firebase-sessions` changelog entry so it's released.\n\n---------\n\nCo-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>",
"message": "Revert \"Make a change to prevent false positive background app starts.\" (#7278)\n\nReverts firebase/firebase-android-sdk#7274\n\nReverting this if the current change is going to be included in M169. \n\nAn additional change is needed to verify that the\n`mainThreadRunnableTime` should be set only if no activity's onCreate\nhas been called - otherwise this can cause a regression of *genuine*\nbackground starts.",
"message": "Make a change to prevent false positive background app starts. (#7274)\n\nAdded a change in `AppStartTrace` to prevent false positives of a\nbackground app start on API 34+ devices.\n\nSee https://github.com/firebase/firebase-android-sdk/issues/5920\n\nVerified locally:\n\n```\n2025-08-20 10:34:51.283 18373-18373 AppMonDemo com.tdeshpande.appmontester D mainThreadRunnable.run(): activityCreated = false\n2025-08-20 10:34:51.292 18373-18373 AppMonDemo com.tdeshpande.appmontester D onActivityPreCreated: mainThreadRunnableRun = true\n2025-08-20 10:34:51.294 18373-18373 AppMonDemo com.tdeshpande.appmontester D onActivityCreated: mainThreadRunnableRun = true\n2025-08-20 10:34:51.314 18373-18373 AppMonDemo com.tdeshpande.appmontester D onActivityStarted: mainThreadRunnableRun = true\n2025-08-20 10:34:51.318 18373-18373 FirebasePerformance com.tdeshpande.appmontester I Firebase Performance Monitoring is successfully initialized! In a minute, visit the Firebase console to view your data: \n2025-08-20 10:34:51.319 18373-18373 FirebasePerformance com.tdeshpande.appmontester D onResume(): com.tdeshpande.appmontester.MainActivity: 74362 microseconds\n2025-08-20 10:34:51.320 18373-18373 AppMonDemo com.tdeshpande.appmontester D onActivityResumed: mainThreadRunnableRun = true\n2025-08-20 10:34:51.323 18373-18431 FirebasePerformance com.tdeshpande.appmontester I Logging trace metric: _as (duration: 74.362ms). In a minute, visit the Firebase console to view your data: \n```",
"message": "Refactor RCM fetch random delay to not depend on FirebaseApp initialization. (#7214)\n\nThis should help address the issue where there could be a deadlock if\n`FirebaseApp` is still being initialized.\n\nSee https://github.com/firebase/firebase-android-sdk/issues/4831",
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?v=4&size=40){kind=avatar}
0 commit comments