Fixed
Status Update
No update yet.
Comments
il...@google.com
il...@google.com
Not starting yet? It's already "Early in March" enough (Mar/14/2018 PDT)
va...@google.com
Masashi & all, thank you for enquiring about this.
The opt-in period has been moved to April 2018. We'll be sure to update this thread when closer from the exact milestones.
The opt-in period has been moved to April 2018. We'll be sure to update this thread when closer from the exact milestones.
il...@google.com
al...@gmail.com
As outlined in the recent release notes for the Maps Android API [https://developers.google.com/maps/documentation/android-api/releases ], this feature is now available for the new basemap style.
To opt-in, add the following tag to your AndroidManifest.xml file, within the <application> tags. The user's device must have at least Google Play Services version 12.0.0 in order for the opt-in to work.
<meta-data android:name="com.google.android.gms.maps.API_OPTIONS" android:value="B3MWHUG2MR0DQW"/>
To opt-in, add the following tag to your AndroidManifest.xml file, within the <application> tags. The user's device must have at least Google Play Services version 12.0.0 in order for the opt-in to work.
<meta-data android:name="com.google.android.gms.maps.API_OPTIONS" android:value="B3MWHUG2MR0DQW"/>
va...@google.com
The new basemap style will switch from opt-in to opt-out within the next few weeks.
Should you wish to temporarily opt-out, add the following tag to your AndroidManifest.xml file, within the <application> tags:
<meta-data android:name="com.google.android.gms.maps.API_OPTIONS" android:value="B3H9HE845CFHYG"/>
We will keep posting updates here closer to date.
Should you wish to temporarily opt-out, add the following tag to your AndroidManifest.xml file, within the <application> tags:
<meta-data android:name="com.google.android.gms.maps.API_OPTIONS" android:value="B3H9HE845CFHYG"/>
We will keep posting updates here closer to date.
ap...@google.com
The switch from opt-in to opt-out of the new basemap look for the Maps Android API will be effective within the next 24 hours.
jb...@google.com
The new basemap look is now live for the Maps Android API. Please look at https://developers.google.com/maps/documentation/android-api/releases .
Description
Compose provides
rememberSaveable, along with accompanying tools likeSaverandSaveableStateRegistryas its mechanisms for storing saved instance state. Currently, there isn't a provided interoperability layer between these tools andSavedStateHandle.If
SavedStateHandleisn't used in theViewModel, state that is hoisted from@Composables toViewModels won't be stored to saved instance state. This might either cause bugs due to state loss upon process death, or act as a barrier to hoisting state sufficiently if it seems likerememberSaveablehas to be used to remember state across process recreation.The proposal is to provide the necessary hooks for
SavedStateHandlewithSaverso that any state holder that is being saved viarememberSaveablecould also be saved withSavedStateHandle.