Fixed
Status Update
Comments
se...@google.com <se...@google.com> #2
Not starting yet? It's already "Early in March" enough (Mar/14/2018 PDT)
se...@google.com <se...@google.com> #3
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 <il...@google.com> #4
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"/>
ap...@google.com <ap...@google.com> #5
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.
Description
The keys() method in SavedStateHandle will always include keys for values set via the set() method, but it doesn't include the keys associated with a SavedStateProvider set via setSavedStateProvider() until after state is saved. If you wanted to remove all of the SavedStateProviders by iterating through the keys, whether it would work or not would depend on if state was already saved, which is kind of inconsistent and seems like a bug.