We have our application live on production. Is using an Facebook App ID for Business and is currently in use.
Before deploying updates to production we first test them on staging which uses a Facebook Test App cloned from the main App.
Right now we implemented a new functionality on staging which uses some new permissions. We tested it and is ready for deploy but first we need those permissions approved on production so our users can use it.
I can't see any App Review button on the Test App inside the App Dashboard on Facebook Dev. The solution would be to ask for those permissions on production but we haven't deployed there yet because the app is currently in use and the new funtionality will not work without those permissions from the start.
Any idea of what we can do to get those permissions approved on production?
Related
We have android application that uses Fitness API for reading steps.
Our app has passed OAuth verification process and ./auth/fitness.activity.read scope was approved:
In the app we request "fitness read" permission using this part of the code:
val fitnessOptions = FitnessOptions.builder()
.addDataType(DataType.TYPE_STEP_COUNT_DELTA, FitnessOptions.ACCESS_READ)
.build()
GoogleSignIn.requestPermissions(
this,
1000,
GoogleSignIn.getAccountForExtension(requireContext(), fitnessOptions),
fitnessOptions
)
But unverified OAuth consent screen still appears:
GCP Technical Support didn't help with it and asked us to report this problem here.
Any ideas what's wrong? Maybe someone had similar issue?
That screen indicates that your app is in "testing" state: https://support.google.com/cloud/answer/10311615#zippy=%2Ctesting.
You will need to switch your app to production state. Before doing so, please confirm that your app is requesting only scopes that it has already been approved to use. If your app is using any sensitive scopes that are not approved, your users will see an unverified app screen. You can determine what scopes your app is using by inspecting your code.
The problem was in OAuth Client ID.
We had 2 projects in Google Cloud Console: for prod and for dev.
OAuth consent screen was verified for prod one.
Prod and dev projects had Client IDs for the same package name and certificate and my prod app has used Client ID of the dev project.
I'm trying to migrate my app from Fabric to Firebase. In Fabric dashboard, it shows like this:
Great. I go to migration screen to migrate, but I see this (the bottom most is the same exact app:
It shows as migrated, even though it's in the list of "not migrated" apps. It says migrated by an admin, and I'm the only admin. I go to Firebase (there are 2 possible accounts that I may have migrated it in the past just in case I don't remember) in my both Google accounts, but it's not there either.
What am I doing wrong?
This is a UI discrepancy you're seeing. Your app was very likely migrated by a previous account owner, and they did not give you permission to view the app in Firebase. I recommend writing into support at support(at)fabric(dot)io and they will check your bundle ID in the backend and confirm this suspicion.
We are working in RingCentral application and APIs with SMS and fax permissions.
The application recently moved to production from Sandbox environment.
We have now a requirement to add 2 additional permission ReadAccount, ReadContact in the app which was not added during sandbox testing.
How can we do that? I don't see any option to modify the app. Is there any way we can modify the existing app?
As per I know once your app is in production, you cannot change anything.
You need to ask devsupport#ringcentral.com for any help. Once they added the permission with your request (not sure if they do.. most probably they don't) you need to test again for that permission you acquired.
The official recommendation is to create a new app, add proper permissions and graduate it. So in that case you need to go through again.
As per the reference here
"You can clone the app, give it a new name or add a version to the new app name. Add the missing permissions and run test in the sandbox the same way as you did for the first app. Graduate your app and finally replace the client Id and secrete to use the new app. You can suspend the old app after that."
Similar question here: https://forums.developers.ringcentral.com/questions/1059/how-to-add-permissions-of-read-call-log-in-product.html
testing our app when running on xcode is good and we can see ads even without test mode (device hash), so we can see live ads. Everything is setup fine, but when we test the app on test flight, It's always returning a log of "No Fill".. :S,
We have logged in the facebook native app, Limit ads tracking is disabled..
What do you think is still the problem? Is it required from facebook that the app is live on apple store?
Thank you very much!..
The issue is in TestFlight.
By design, TestFlight generates a new and different IDFA in each run. Those IDFAs are different from your device IDFA which is used by Facebook native app. When your app sent ad requests with those new IDFAs to Audience Network, the server cannot matching the IDFA to get the proper ads and returns 'NO FILL' back. That is what exactly you have experienced.
Here is the link for detail:iOS: TestFlight beta app get new advertising identifier in each run.
The solution is to get off TestFlight and run the app directly through the device, or continues to use TestFlight but with Facebook test ad only.
Is there any way to test your app or plugin before submitting for approval?
Or is there any sandbox for BigCommerce to test the apps prior?
How were the developers of the apps that are presently in the BigCommerce store able to test during the development phase?
You can test your app in a free trial store.
You can do this by:
Setting up a developer account
Logging in to the Apps section
Adding a draft app
Logging in to any Bigcommerce store (preferably a trial store) where you are an admin
Go to Apps then My Drafts
Install your app & test away
See https://developer.bigcommerce.com for more info.
To test your app on local, use ngrok.io to create a https url that tunnels to your localhost