I received email from google :
We are writing to remind you that the previous versions of Places SDK for Google Maps Platform were deprecated on January 29, 2019, and will be turned off on July 29, 2019. This email is our final reminder before the previous versions are completely shut off.
List<Place.Field> fields = Arrays.asList(Place.Field.ID, Place.Field.NAME, Place.Field.ADDRESS);
Intent intent = new Autocomplete.IntentBuilder(
AutocompleteActivityMode.OVERLAY, fields)
.build(activity);
activity.startActivityForResult(intent, IntentParams.REQUEST_SELECT_PLACE);
app level build.gradle:
implementation 'com.google.android.libraries.places:places:1.0.0'
project level gradle:
classpath 'com.google.gms:google-services:4.2.0'
What more changes do I have to do?
Related
Currently building out a bot in Bot Framework Composer and deploying it on the Teams client. I suddenly am having issues since last week where my custom telemetry ("telemetry - track action") is no longer showing any results in Application Insights. The few that did also only save one property and not the others (see image below). Other events (LUIS, bot message received, etc) all show up in real time and correctly.
The only telemetry event that saved in the past week (there should be at least 10 saved), with only one property logged
The telemetry event and its properties
This is a known bug in Microsoft.Bot.Builder.Dialogs.Adaptive.Runtime version greater than 4.15.0
There is a pull request for this issue and most likely will be fixed in next release of botbuilder-dotnet
PR https://github.com/microsoft/botbuilder-dotnet/pull/6391
A workaround for now is to downgrade the Adaptive.Runtime package to 4.14.0
To learn how to downgrade packages in .NET, here is doc to Install and manage packages in Visual Studio using the NuGet Package Manager
I'm not able to call the places API
Error: The operation couldn’t be completed. The Places API for iOS is
not enabled. See the developer's guide
(https://developers.google.com/places/ios-api/start) for how to enable
the Google Places API for iOS.
I've followed this guide Places API getting started:
1) Install the API (Pod file and pod install)
2) Setup the API Key and restrict it to iOS
3) Add the key in AppDelegate (GMSPlacesClient.provideAPIKey("YOUR_API_KEY"))
However, I'm still hitting the above-mentioned error.
Is this the correct API to enable?
I've waited for more than 30 mins (more than 17 hours now)for the API key settings to take effect but the error still persist. I'm able to use the same key to get Maps API to work though.
Version: "GooglePlaces (2.7.0)" + iOS12.0
Works after updating the version in Podfile from 2.7.0 to 3.0.3
pod 'GooglePlaces', '= 3.0.3'
pod 'GooglePlacePicker', '= 3.0.3'
pod 'GoogleMaps', '= 3.0.3'
Installing GoogleMaps 3.0.3 (was 2.7.0)
Installing GooglePlaces 3.0.3 (was 2.7.0)
Just noticed there's a note in the documentation which states:
IMPORTANT: The Place Picker is deprecated as of January 29, 2019. This
feature will be turned off on July 29, 2019, and will no longer be
available after that date. To continue using the Place Picker
through the deprecation period, do NOT migrate to the new SDK yet,
and do NOT disable the Places SDK for iOS service in your Google Cloud
Platform project, as doing so will also disable the Place Picker.
Apparently it's not working now although it mentioned that it will be turned off on July 29, 2019. Perhaps I need to revert the code to use the prior version.
Currently using Facebook Ads SDK for Java v2.9 and trying to upgrade to v2.10 or v2.11. However, neither of the newer versions has the method getFieldImpressionDevice on the AdInsights object? I haven't found any change log info that discusses a change or deprecation around this call. Anyone have any insight into this problem?
Also a little confused as to why github :
https://github.com/facebook/facebook-java-ads-sdk/
doesn't have the 2.10 or 2.11 libs only the 2.9 libs even though this link indicates it, eg.,
src/main/java/com/facebook/ads Ads SDK v2.11 Release Nov 8, 2017
Thanks for any help
There's a known issue it turns out. Some (or all) of the breakdown fields and methods in the AdsInsights class were left out. It can be worked around using raw json, eg.,
JsonObject jo = insight.getRawResponseAsJsonObject();
JsonElement je = jo.get("impression_device");
String device = je.getAsString();
How do i make sure my app can run on android devices below Lollipop( version 4.03 to 4.42). I watched a xamarin university video that says xamarin forms supports android version 4.03(ice-cream sandwich) and upwards. I also read about runtime checks and feel like this might be the answer to my problem, but how can i write runtime checks for android when basically all my ui and logic is contained in the PCL project?
The first thing to do is ensure you are using the Android AppCompat library. I think new projects use this by default now. If you have an older project that doesn't follow these instructions to update. This will allow your app including any Material Design look and feel to run on older versions of Android.
If you do things differently based on Android version, put the code for this in the Android project and use dependency service to call it.
Like this:
if (Android.OS.Build.VERSION.SdkInt >= Android.OS.BuildVersionCodes.Lollipop)
{
// level specific code here
}
I am using TestFlight to distribute test versions of my app to a private group of people. As I am making a lot of updates these days I wonder if some of my testers will get sick of the large amount of update emails they receive.
So I thought it would be a better approach to let the app check for updates when started and than showing a small notification that there is a new version out and to only notify the testers about important updates by mail.
So my question is: Is there a way to retrieve information about new builds by RSS or some other channel?
Thanks.
The TestFlight iOS SDK already supports this for beta versions if you have the SDK integrated into your app:
Beta In App Updates
If a user is using a beta version of your app, you are setting the
UDID, a new beta version is available, and that user has permission to
install it; an in app popup will ask them if they would like to
install the update. If they tap "Install", the new version is
installed from inside the app.
NB: For this to work, you must increment your build version before
uploading. Otherwise the new and old builds will have the same version
number and we won't know if the user needs to update or is already
using the new version.
To turn this off set this option before calling takeOff:
[TestFlight setOptions:#{ TFOptionDisableInAppUpdates : #YES }];