I'd like to know how to correctly follow the best practice for api v2. I'm currently unable to re-ask a declined permission on mobile (6.1 release note fix this on canvas, still not working on mobile with sdk 6.2b), there's no FBSession or FBAccessTokenData equivalent (present in ios or android sdk), so we have to call FB.Api to get permissions, cannot get declined permission. Json returned by FB.api differ from graph tools
f.e. :
graph tool for /me/permissions => { "data": [{"permission": "permissionName", "status": "granted"}, ...] }
unity sdk => { "data": [{"permissionName": 1}, ...] }
Will the facebook sdk evolve to offer the same features as native plug in or should I use another sdk ?
Related
I'm currently working on a plugin for wordpress, in which I have to use Google Analytics Reporting API and Facebook's Graph API.
Now everything is working fine with their respective php SDKs, the only problem is both are very large and not suitable for a plugin.
I'm only using Google Analytics Reporting API and oAuth from google sdk and some functions of Graph API.
What can I do to reduce size of the sdk?
Thanks!
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.
I am using dynamoDB in my application ,
but I need my application to work in the offline mood too ,
so I am trying to use appsync for the offline mode .
but I don't know if it is available for xamarin or not
I see in its documentation that it supports android and ios ,
but did it support Xamarin (directly or even implementing it in android and ios native first then attach it to Xamarin ? )
appsync documentation : https://docs.aws.amazon.com/appsync/latest/devguide/welcome.html
and if it is available is there is any tutorial or sample code for this ?
any help please ?
Thank you .
Well, I think you should go through their documentation for Xamarin and .Net
In the Setting Up the AWS Mobile SDK for .NET and Xamarin, they have given their own samples to refer to!!
Following are the links for each service that they provide for Xamarin
Cognito Identity
Cognito Sync
Dynamo DB
Mobile Analytics
S3
SNS
From what I understand App sync is not a part of the available official SDK's
But if you check the GitHub issue for the same which is here https://github.com/aws/aws-sdk-net/issues/901 and check the comment by NeilBostrom he has a way of doing it through GraphQL
Goodluck!
Feel free to get back if you have queries
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.
i need a list of my application users.
i use facebook C# sdk
You should store your application users ids on your own...
Currently this isn't possible with API Facebook providing.
BTW,
Official Facebook C# SDK is deprecated so you may want to work with unofficial C# SDK hosted on Codeplex