I have been unable to retrieve the secret key for my REST API app in SANDBOX mode, although it is being displayed when in LIVE mode. I've tested with multiple browsers and on multiple terminals, and the SHOW button is just not responding in sandbox mode. I have also tried creating a new app, but the same issue persists with that too.
Has anyone else faced this issue? Could I have missed some step or requirement? The first app is an old one, created more than a year ago, and I was able to retrieve the secret key and test it sandbox mode then, and it is still working now.
Thank you for your kind attention.
I was also facing the same exact issue. This seems to be a Paypal problem, but here is a solution. Open up Internet Explorer and select your app from your Sandbox account. Once you are on the page with the API Credentials, open up Developer Tools. Choose the Debugger option, which will show you the source code. In the Find command in the Debugger (Cntrl+F), enter "secret selectable". You will find the secret key in the lines next to it. If this doesn't work, manually scroll through the code, and you will find your secret key next to the id tag "show-secret".
Related
I created a DialogFlow app that works perfectly in my developer account.
But I need to test it as another user, so in my Google Action simulator, I added another test account as a OWNER to the project.
I verified this user has OWNER status in both the DialogFlow and Google Action UI.
They are able to edit both projects with full access.
However, when the test account tries to use the simulator it says:
Sorry, this action is not available for your app. Sorry, this action
is not available for your app. In the simulator, you are only able to
invoke actions that you have added to your app. For more information
on how to invoke your app, click here
https://developers.google.com/actions/discovery/explicit
This makes no sense to me:
I verified the test user has OWNER/ADMIN status on both DialogFlow and Google Actions for the project.
In DialogFlow, I verified the Google Assist is pointing to Default Welcome Intent as the default intent.
In Google Actions, I verified that the Default Welcome Intent is visible on the BUILD > ACTIONS UI.
As others suggested, I tried renaming the app several times with no luck.
I tried publishing an Alpha version, with still no luck.
My gut tells me it is some sort of permission/visibility problem, but I am completely stuck. Any ideas would be of great help.
EDIT:
THIS ISSUE HAS BEEN SOLVED. SEE COMMENT BELOW.
"I revisited my activity controls and noticed my "Web and App Activity" had a special clause due to organization permissions. I completely missed it due to the confusing UI. Posted a picture in the main thread. Thanks for reminding me to double check that area."
After you asked your company admin to enable this feature, it should be same as the image in below.
This error message is quite misleading. I have encountered this error a couple of times, and generally the problem was with one of the privacy settings in my Google account.
In this case you should go to https://myaccount.google.com/activitycontrols, confirm that you are logged in using your test account, and make sure the following are enabled:
Web & App Activity
Device Information
Voice & Audio Activity
I am using parse facebook login for new users of my app. Most users are able to use it without a problem and I have successfully tested all Facebook login scenarios. Some users, however, report that when they press the login button they see brief activity indicator and then nothing happens. In code, no error is registered but the user is not brought beyond the login page to the app's initial screen. The problem resolved if the user deletes the app from their Facebook app settings and then tries again. Has anyone else experienced this and/or found a solution? Thanks
Not sure if this ever got resolved for you.
There are multiple possible causes for this of course including your own code. However, we've seen a similar issue with 2 causes / solutions.
UX-wise we detect multiple failed logins (typically with no error code) and then pop a notification telling the user how to solve. Still digging for a code-level solution that'll solve either of these issues permanently (if you found one, please post!) but hope these help & let you know you're not crazy.
Issue #1: User is logged into multiple Facebook accounts from the same device (e.g. a primary account and an org or 2ndary account).
Fix #1: Have user log out of all Facebook instances (app, safari, iOS settings) and then log back in.
Issue #2: User has rejected Facebook permissions.
Fix #2: For iOS, make sure Your App is toggled on in Settings -> Facebook -> Your App
I am following the Scrumptious sample that is on the FB Developers site (https://developers.facebook.com/docs/tutorials/androidsdk/3.0/scrumptious/authenticate/) I successfully implemented everything up to the end of step 2 without any errors.
But i noticed that if i have the Android FB Application installed on my device then it does not log in.
It asks permission to access my public profile and friend list (to which i reply OK). After that it execute onSessionStateChange() but state = CLOSED_LOGIN_FAILED.
I did verify that:
My app is listed on https://developers.facebook.com/apps
I checked and my Native Android App option is ticked
i also have my Package Name, Hash Key entered.
The Facebook Login option is also enabled.
Please can someone help me to get this working :-( i am
struggling with this for 2 days already and no luck.
Thanks.
Problem has been resolved. After i generated the HashKey using the KeyTool.exe and entered the password as android it gave me a different key. I copied this to the dashBoard on Facebook and it worked. Sorry for wasting your time
I recieved two emails from facebook to put privacy policy link but I couldn't do it in time. I had over 8000 active users and now none can connect onto my forum. I guess they terminated the app? I did add the link onto my app but still it isn't working. I have looked around to see If anyone else went through the same. How do I contact Facebook and get this resolved.
I guess they terminated the app?
Check your app dashboard – usually, as a first measure, your app gets put into sandbox mode.
Add the missing policy links, and then try taking it out of sandbox mode again.
Steps:
Our app recently switched to using App Access Token for open graph. Following is the URL using which the action is being published:
https://graph.facebook.com/FACEBOOKID/namespace:action
The publish works fine and id is being returned. Also following url returns the app activity with the details of new activity that was created using URL above:
https://graph.facebook.com/FACEBOOKID/namespace:action?access_token=app_access_token
Problem:
Activity published is not visible on old Profiles that dont have timelines activated. It used to work fine when access token was being used instead of app access token. Switching profile to use timeline shows the activity though.
I have been googling to find if anyone else is facing the same issue but havent been able to find concrete answer. Am i missing something in terms of app configuration or is this a known behavior? Thanks in advance for all the help.
Timeline will become mandatory for every user soon, so I wouldn’t worry about this much …