Stack: Expo React Native, expo-branch
I am searching for a way to track Facebook Campaign Ad Installs with Expo in the managed workflow. I have integrated expo-branch (link below) and set up the integration between Facebook Ad Manager and Branch. As it stands, Branch is not getting the IDFA, which I suspect is the reason I am getting no analytics on Facebook through any ad campaigns. It looks like Expo has restricted access to the IDFA and I'm wondering if anybody has found a viable workaround (without detaching from Expo).
References:
https://docs.expo.io/versions/latest/sdk/branch/
https://forums.expo.io/t/latest-expo-branch-excluding-the-idfa-code/44357
A Branchster here:
For SAN(self attributing networks) like Google and Facebook, it is necessary that the Branch SDK correctly captures the device identifiers for the SAN integration to work and you be able to see attributed Installs and downstream events. Since there is not much support for Expo in the managed workflow, we would suggest using Bare workflow. Alternatively, you can reference our complete SDK support here.
Related
Can I publish an agent version on an environment using the Dialogflow V2 API?
I can't find any documentation on how to do that.
The doc about versions and environments only mentions doing this using the console (https://cloud.google.com/dialogflow/docs/agents-versions).
And the API doc of the agent environments resource only contains a list method (https://cloud.google.com/dialogflow/docs/reference/rest/v2/projects.agent.environments).
Does it mean that every change done using the API is automatically reflected in production?
Or does it mean that every change done by API is staged, and can only go to production by manually accessing the console and publishing the new version?
Both options seems terrible by the way.
Currently, it's not possible to manage agent versions through the Dialogflow API, it seems that this feature is already being contemplated to be integrated to Dialogflow; however, there is no an ETA for its implementation. You can follow up this request here.
I have basic understanding of .net and chatbot.
I wanted to integrate Amazon lex in xamarin(ios, android)app. There seems to be no example or sample. I have created chatbot from AWS platform intent and slots.
Also I wanted to use database to get query return. Any sample to integrate AWS Lex with Xamarin app would be helpful.
As I understand from your question, you already have some implementation of chatbot made with AWS services, but you are having issue on integrating it to your xamarin application to be able to use it in IOS and Android devices.
For that purpose, there is AWS Mobile SDK which happens to support also xamarin.
From their link:
https://docs.aws.amazon.com/mobile/sdkforxamarin/developerguide/Welcome.html
I also did not find a Lex tutorial directly, but a very promising quote:
Supported AWS services currently include, but are not limited to [narrow list of services]
was on the same page. I looked around, found this text:
The AWS Mobile SDK for .NET and Xamarin also allows you to use most of the AWS services supported by the AWS SDK for .NET. The AWS services specific to mobile development are explained in this developer guide. For more information about the AWS SDK for .NET, see [a link]
clicked the link and ended here:
https://docs.aws.amazon.com/sdkfornet/v3/apidocs/Index.html
and under link AmazonLex -> AmazonLexClient there was something, you probably wanted to see:
Version Information
.NET Standard:
Supported in: 1.3
.NET Framework:
Supported in: 4.5, 4.0, 3.5
Portable Class Library:
Supported in: Windows Store Apps
Supported in: Windows Phone 8.1
Supported in: Xamarin Android
Supported in: Xamarin iOS (Unified)
Supported in: Xamarin.Forms
Those 3 last let me understand that whenever you setup Mobile SDK, you get access to AWS services in Xamarin, also Lex.
Steps to install on
https://docs.aws.amazon.com/mobile/sdkforxamarin/developerguide/setup.html
mainly contain steps on how to create xamarin app and get AWS account, most important is to install the AWS Mobile SDK for .NET and Xamarin and configure it. More detailed steps are under that link.
After that the process is to follow the instructions on:
https://aws.amazon.com/getting-started/projects/bots-just-got-better-net-toolkit-lex-lambda-cognito/module-one/
like pointed in comments. I suppose once you have access to any service via Mobile SDK, the wire up of Lex may go in similar steps and no special just xamarin tutorial is not needed anymore.
It seems you are looking for both architecture and sample code for implementing AWS Lex bot with .NET backend that can be integrated with iOS/Android Frontend.
You have multiple choices here to do it
Build both chat user interfaces in iOS and Android and integrate them AWS iOS & Android SDKs to utilize the AWS LEX bot.
Just implement a bot user interface in iOS and Android app and integrate it with a .NET backend that can utilize AWS .NET SDK to integrate with your LEX bot.
I would recommend the second approach as it will save you writing the LEX integration code twice both in Android and in iOS. In the second appraoch you will be able to write a single integration for AWS LEX in .NET and that can give a unified experience across the mobile devices(iOS/Android)
Now for the .NET based backend integration with AWS LEX bot.
If you are an experienced .NET developer and you know how will you host your code then only thing that you need is the .NET API reference for AWS LEX, which can be found here
https://docs.aws.amazon.com/sdkfornet/v3/apidocs/items/Lex/TLexClient.html
But if you are not sure how to write this integration code and also not sure how the deployment will look like then you can follow the below tutorial
Bots Just Got Better with .NET and the AWS Toolkit for Visual Studio
Also, find here the architecture form the above tutorial
there is no direct solution like Amazon Lex is supported by React-native. i confirmed with xamarin team as well as AWS service one of the member. direct integration not possible.
We know how to call Facebook Graph API v1.0 and are calling it in the iOS SDK (https://developers.facebook.com/docs/apps/upgrading) but new users are getting treated as though they're signing up with v2.0.
We know that once a user logs in via Graph API v2.0, there is no going back to v1.0 for that individual user (http://code-worrier.com/blog/changes-in-facebook-graph-api-2-dot-0/) but does anyone know if all new users to your app will automatically login through v2.0 and only previous users can login v1.0? We're using the Facebook iOS SDK v3.14.
Thanks so much.
New users signing up for your application since 4/30/2014 will return app-scoped id's. The version you use in the URL for the API request won't change that.
Here's what we found out: you can still log into / use the old version of the Facebook API (v1.0). The issue is the API version that gets called by your app depends on the Facebook iOS SDK version you are using in your app. So if you want to jump back to pre-v2.0 Facebook API, you need to be using an old version of the Facebook iOS SDK (3.13.1 and previous). They are all found here: https://developers.facebook.com/docs/ios/downloads
Keep in mind, Facebook is forcing developers to upgrade to v2.0 by April 30th of 2015. But, if you have a v2.0 headache now that you don't want to fix right away, this a decent band-aid solution. In our app, we upgraded the Facebook iOS SDK to get compliant with Apple's IDFA regulations, not knowing we were upgrading to v2.0 of the Facebook API. Since our app uses some features no longer available in v2.0, this was a huge issue.
Any users that may have signed up for your app while you were using v2.0 may need to delete app related info on Facebook so that they can log in fresh when you jump back to v1.0. This will allow you to get real Facebook user IDs and not app scoped user IDs.
The last small hurdle is that Apple is now rejecting many, if not all, apps that use the IDFA. All Facebook SDKs that use v1.0 use the IDFA (to my knowledge). The only way around it is to tell Apple that you are using it, but that it is attributed to a previously served advertisement (you do this on iTunes connect). See this article here: http://www.adexchanger.com/mobile/apple-throws-a-bone-to-app-marketers-blesses-idfa-for-attribution/
Again, this is not necessarily a 'proper' solution, but if you don't have the bandwidth / resources to fix your v2.0 issues right now, it can definitely help. Just make sure to get back to v2.0 before April 30, 2015.
We have an existing Android and iOS application that consumes REST API from our servers. The API provides a token to the authenticated users after they log in using their credentials (username, password combo.) from the mobile applications.
Now, we're planning to create a Google Glass application for the same. In this case, we'd like to use the existing REST API along with Glass also. The Glass app will be built natively using the GDK.
My concern is, how would the users be able to input credentials? Because, users may have signed up for the service using non-google accounts?
Many thanks in advance.
At the moment, there is no supported way for apps made with GDK Early Access to authenticate the user or provide a way to connect the Glass account to your auth system. The Glass team has indicated such methods are coming, however - the Strava Cycling app, for example, does this, and it is expected that a similar feature will become widely available as the GDK matures.
Strava Cycling appears to get its credentials at the time you setup the app through MyGlass. When you turn it on it redirects you to a website to log into Strava's service before completing the install.
I just gave a talk on this exact topic at Wearables DevCon. The solution I proposed is purely done through GDK. All the user has to do is sign into their Google Account on a phone/tablet/computer and enter a code that is shown on Glass.
Check out the slides here:
https://docs.google.com/presentation/d/1NepYwlKdEvLV0QH9ix2I8l-JY1kHjBR9AXKBNpgTI6g/edit
And the code here:
https://github.com/victorkp/GlassWebNotes
The latest Glass release (XE16) publishes the remote authentication API for apps distributed through MyGlass:
https://developers.google.com/glass/develop/gdk/authentication
My team is trying to develop a product for the google apps marketplace and I am having issues with the workflow in the new ADMIN SDK.
With the now deprecated Provisioning API we simply ask for a username and password from the account we are trying to manage.
With the ADMIN SDK it seems as though they would need to go enable the API, create a key and do a lot of manual work for this to happen. This really is a tough option for us as the technical level of our clients is not likely to be able to make this transition.
Is there something like the work flow for the provisioning API where they can enable management from a third party or a recommended workflow for a developer to build an application that can access any number of google apps accounts?
A use case for this is say I want to develop a different option for a console, I want to build a console web app and simply ask for credentials or easy setup routine and allow our users to manage their google apps account in a different way.
Thanks in advance,
Steve
The Admin SDK Directory and Reports APIs work correctly with 2-legged OAuth 1.0a which is what the Google Apps Marketplace currently supports and automates. You do need to turn the Admin SDK on under "Register for additional APIs" from your Vendor Profile page on the marketplace. Also, the Administrative APIs for the domain must be turned on. You'll get a generic error that the domain cannot use the APIs if it's off in which case you can direct the client to the exact CPanel page where they can turn it on.