Fabric shows project as not migrated to Firebase, but in migration screen it shows as migrated - crashlytics

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.

Related

Is possible to get Facebook Graph API permissions on production from a Facebook Test App?

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?

Add permission in the app in RingCentral production

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

Detecting Installation Source with react-native-fbsdk

I'm facing a problem with react-native-fbsdk. I'd like to know whether the user has installed the app by coming through Facebook Ads or has he/she installed it organically from store (App Store, Play Store). Is this even possible with React Native?
The reason is, I need to log events for analytics restricted only on installations done via Facebook. There are pre-defined events, like App Installs and App Launches tracked, but my events are custom events.
I have assumption that either AccessToken.getCurrentAccessToken() or AppEventsLogger.getUserID() would return something when the installation is performed through FB. On dev environment, both returns null which is kind of expected. However these ideas could only be tested on production and this isn't an option.
So the actual question is: "How do I detect whether the user is coming through Facebook advertisement link?"

Adding a Sandboxed app to Login Items

I have read through many questions here about launching my app on login. I have followed this awesome tutorial suggested many times. That tutorial does work. BUT...
The one side affect that comes from using a helper app and registering it using SMLoginItemSetEnabled is that my app does not show up inside the user's Login Items in System Preferences.
There are several apps in the App Store (such as PopClip and Dash) that do what I am trying to do. I just can't figure out how...
UPDATE: I found out from the Dash developer that Dash is actually not sandboxed. He also believes that PopClip is not either. This could explain things... https://alpha.app.net/kapeli/post/3975968
UPDATE #2: I just got confirmation from the PopClip dev that it indeed is not sandboxed as well. https://twitter.com/pilotmoon/status/313746294361427968
With the last 2 updates, I guess the answer is clear. As of today, there is no way to accomplish this with Sandboxed apps.
Hope it's not too late.
In Apple's "Daemons and Services Programming Guide":
Adding Login Items
There are two ways to add a login item: using the Service Management framework, and using a shared file list.
Login items installed using the Service Management framework are not visible in System Preferences and can only be removed by the application that installed them.
Login items installed using a shared file list are visible in System Preferences; users have direct control over them. If you use this API, your login item can be disabled by the user, so any other application that communicates with it it should have reasonable fallback behavior in case the login item is disabled.
In sandboxed environment, only Helper applications can be installed in login items. You need to create one, stored in the Contents/Library/LoginItems folder of the main application.
Then you can used SMLoginItemSetEnabled to set the helper as login item and ask the login item to start the main application.

"Create App" button is missing on a verified developer profile

I used to be able to create facebook apps a few months ago using my personal profile. Now I got back to development again but unable to create any apps for a simple reason that the page https://developers.facebook.com/apps does not have a Create App button any more.
My account is verified, I had activated the facebook developer app before (even though I do not see in my app list for some reason now), I am logged in as a person, not as a page admin and I have created apps before using exact the same account.
What could be wrong?
It's a known problem that looks about consistency on developer data.
The solution I posted here Facebook - Unable to create an app
go to https://developers.facebook.com/setup
I've been fighting with this issue for hours! I think it happened because I haven't created an app since facebook transitioned to the app center. Going directly to https://developers.facebook.com/setup fixed my issue!