I have an Android app and Facebook developer portal has requested me to upgrade.
According to the API upgrade tool, it has 3 items
Items to fix to upgrade Graph API from v2.6 to v3.0:
Facebook Login2.0 - In v2.7 of the API, you will need to request business_management to manage your business account. (New)
GET {user-id}/permissions2.0 - Starts enforcing the app's restrictions (such as country or age ) on API calls made without the application's ' appsecret_proof'in the request. (Change)
GET {user-id}/permissions2.0 - GET /{user-id}/conversations and GET /{page-id}/conversations will return fewer fields by default. Use the 'fields' param to explicitly ask for the set of fields you want. If you ask for an explicit set of fields, the response will not contain any extra fields that you did not ask for (Change)
its not really clear what are the steps to upgrade. Can anyone give some guidance. Thanks
Ok I already managed to update it just by change the version in advance setting at developers.facebook.com It looks like the thing that it told to fix in update tools just apply if you use that particular code only
Related
I am creating a phonegap app and it has 2 variables to set PayPalEnvironmentProduction & PayPalEnvironmentSandbox in paypal.js file.
I logged in to my developer.paypal.com account and there i can see "v.zero SDK" & "REST API apps" on URL : https://developer.paypal.com/developer/applications/ .
I am not sure which values should I put for both my variables PayPalEnvironmentProduction & PayPalEnvironmentSandbox.
there are 3 APIs you can pull here. There is an NVP/SOAP as well. So the question I have is What APIs are used in the paypal.js file?
If you see REST APIs denoted by Client/Secret (PayPal)(V.0 is for BrainTree APIs) then you'll want to apply for REST APIs; if you see APP ID with user password and digital signature you'll want to use/apply for the NVP/SOAP APIs. Hopefully this helps, let me know if you have more questions as I'd be happy to help.
I want to customizing the source code of Wso2 appm/emm. Therefore I want to know what can we customize and upto what extent, where will I get the code to make changes(from github or with in the product). And also please tell what all I have to do to execute this changed code.
Therefore I want to know what can we customise and upto what extent,
App manager
The given link[1] provides some customisations that can be done.
Additionally, you can customise the app subscription model to add a
custom model such as paid subscriptions.
There is no doc available on UI white labeling, but you should be
able to customise the UI as well by editing the Jaggery apps of store
and publisher.
EMM
Lets say you need to plugin in a new device type that is not
supported OOB, like blackberry. You can write a plugin your self and
implement this functionality.[2]
You can customise the UI[3]
Customise the Email template[4]
White/Customise the Android agent[6]
White label iOS agent[7]
Event reporting[8]
In both products you can customise the management console[5]
where will I get the code to make changes(from github or with in the
product). And also please tell what all I have to do to execute this
changed code.
EMM
Repos to build according to build order,
https://wso2.github.io/github-repositories.html
App manager
Repos to build according to build order,
https://github.com/wso2/carbon-appmgt
https://github.com/wso2/product-app-manager
Prior to working on any code related changes, if you are planing on doing so, I highly recommend you to understand the architecture of the products[9][10]. More information about building WSO2 products is available here[11]
[1].https://docs.wso2.com/display/APPM110/Extending+App+Manager
[2]. https://docs.wso2.com/display/IoTS100/Writing+Your+Own+Device+Connector
[3]. https://docs.wso2.com/display/EMM210/Customizing+the+UI+and+Documentation
[4]. https://docs.wso2.com/display/EMM210/Customizing+Email+Templates+for+Tenants
[5]. https://docs.wso2.com/display/EMM210/Customizing+the+Management+Console
[6]. https://docs.wso2.com/display/EMM210/Customizing+the+Android+APK+File
[7]. https://docs.wso2.com/display/EMM210/White+Labeling+WSO2+EMM+iOS+Agent
[8]. https://docs.wso2.com/display/EMM210/Reporting+Critical+Events+via+Alerts
[9]. https://docs.wso2.com/display/EMM210/Architecture
[10]. https://docs.wso2.com/display/APPM100/Architecture
[11]. https://wso2.github.io/using-maven.html
I had implmented linkedin integartion in my android app using socialauth a year ago. It was working fine till few days back. Now it gives following error:
"org.brickred.socialauth.exception.SocialAuthConfigurationException: Application keys are not correct. The server running the application should be same that was registered to get the keys."
Tried using following default keys also.
api.linkedin.com.consumer_key = bh82t52rdos6
api.linkedin.com.consumer_secret = zQ1LLrGbhDZ36fH8
Getting same error for keys of app generated previously, default app keys and for fresh created app.
Any idea why it is happening? Is there any change in linkedin APIs?
Libs included : socialauth-4.4.jar, socialauth-android-3.2.jar.
This is due to the change in the Linked in developer program.
Changes are mentioned here https://developer.linkedin.com/support/developer-program-transition.
You getting this error because the default scope setting in the r_fullprofile which is as part of the change no longer available.
So to apply this changes in the socialauth API you should pass the scope permission as <prop key="api.linkedin.com.custom_permissions">r_basicprofile,r_emailaddress</prop>
Linkedin have updated their Scope for API , they have updated their APIs link:https://developer.linkedin.com/support/developer-program-transition
The following selection of profile fields are available to all LinkedIn developers:
Basic Profile Fields
Location Fields
Position Fields
These fields are not
Full Profile Fields
Contact Info Fields
Company Fields
Publication Fields
Patent Fields
Language Fields
Skill Fields
Certification Fields
Course Fields
Education Fields
Volunteer Fields
Recommendation Fields.
Additionally
only these Profile API — /v1/people/~ Share API — /v1/people/~/shares Companies API — /v1/companies/{id} will work.
Check your scope.
LinkedIn locked many parts of its APIs on May 12, 2015 according to https://developer.linkedin.com/blog/posts/2015/developer-program-changes
Since you're using the socialauth library, you will have to wait for its developers to push a new version. :(
Downloading 4.9 library solves this issue
You can get the jar from Maven directly:
http://search.maven.org/remotecontent?filepath=org/brickred/socialauth/4.9/socialauth-4.9.jar
I am new to android development and learning. I'm creating an app which stores favorite twitter searches as tags which are clicked on and opened with. In my strings.xml I defined one of the tags as: <string name="searchURL">http://search.twitter.com/search?q=</string>
When I use the http://search.twitter.com/search?q= URL, I'am introduced to:
The Twitter REST API v1 is no longer active. Please migrate to API v1.1.
https://dev.twitter.com/docs/api/1.1/overview
I was wondering, what changes I should make to migrate to new version. Is it a simple change in the searchURL ?
from the link you sent:
At this time, all authentication requires user context, but in the
coming weeks we'll be pushing out support for a form of authentication
not requiring a user context.
I think that perfectly answer your question, isn't it?
First of all I'm sure that my fb app id is valid because users can log in my Android app using facebook credentials until some days ago (I think it's before Feb break change).
Recently new users cannot log in my Android app using facebook any more because facebook keep saying that my fb app invalid (Error is: Invalid application fb-app-id) BUT old users who already authorized my Android app for accessing their info can still log in using facebook. (Old users can still login to my app using facebook credentials but new users cannot)
Does anyone know why this happen to my facebook app and how to fix it?
Edit: When access to https://graph.facebook.com/facebook-app-id I get this error
{
"error": {
"message": "Unsupported get request.",
"type": "GraphMethodException",
"code": 100
}
}
Thanks you.
If you're sure the app is not in sandbox mode (which was gema.megantara's answer), and hasn't been deleted for policy reasons by Facebook the only explanation I can think of is that you've restricted the app demographically (i.e by country or age)
If that's the case the API won't return the app's details unless you make the API call using a user access token for a user who meets whatever restrictions you've applied, and users who don't meet the requirements won't be able to use the app.
If that's what you've done, you can remove the restrictions via the API (via the restrictions field of the Application object or in the ''Advanced'' tab in the app settings in the App Dashboard
If using the frontend interface to change the settings, it's the ''App Restrictions'' field you want to edit, screenshot attached
Basically the same solution as the accepted answer, just updated for the latest FB developer site has been updated so you need do this:
Apps->Your App
Status+Review
Do you want to make this app and all its live features available to the general public? -> Yes
Usually if you get error like that when visit https://graph.facebook.com/523132271032907 is because the sandbox mode is on. Have you try to reset the secret key ?
I think, this is because FB does not check whether application id is valid when the user has already logged in. It likely assumes that if the check passed, the id is valid. Apparently, locking out the users after making the app id invalid has never been a design goal.
try replacing:
<string name="facebook_app_id">CHANGE-ME</string>
with:
<string name="facebook_application_id">CHANGE-ME</string>