Develop Reference

Merge a Facebook login app used for Android with an iOS one, or migrate users to new one

A legacy setup we have means that we have the following:
Facebook app used for login onto Android devices
Separate Facebook app used for login on iOS devices
The issue this has caused is that if a user switches between devices they get a 'this email address is already in use' message from our server.
I need to find a way to get any users logging in on the two platforms to just be able to do so, and i assume the best way to do that is to:
Add Android as a platform on our iOS login
Change the Android app to use the 'other' login/app id (iOS)
Log everyone out on next release of our app (on Android)
Re-authenticate those users on Android as they log in (as we are making them use a new app id)
The key thing is for us however, that
The Facebook login is associated to their entire account (which is hung off the email address) and they have lots of content in there, so we cannot get those Android users to lose anything
We need to let them do this because we WILL already have used that email address if they are logging back in
Will the above strategy work to do this? Any pointers or recommendations on best strategy for this would be hugely appreciated.

You can use this API to link your users across the two apps: https://developers.facebook.com/docs/apps/for-business
Just keep the two apps as separate apps and link them under a single business. Then, when a user logs in you can check if they have already logged in before using the other app.

In Android, ensuring only pre-decided users can only use the app

I'm making an app, which I will distribute via playstore. However, though the app can be installed by anyone in the world, it can only run for selected users who I know.
Below are the possible ways I have figured out,
Check the account E-Mail ids on the phone and if that matches with the one's saved within the app code.
Check the mobile number on the phone and see if that matches with the one's saved within the app code.
When the app runs for the first time, it will send an SMS to my phone. I will reply to that SMS either saying YES or NO. If I reply YES then only the app will run for that user, else it will not.
I would like your feedback on these mechanisms. If there are other ways let me know about that too.
Thanks...

I think your best options are:
Make users log-in using an e-mail and a password (you could ask the user to register and if he uses an e-mail that is known to you, send a password to that e-mail [make the user change it later though])
Beta testing - This allow you to choose wich users will be able to install your app by creating a community on Google+ to beta test your app.
Maybe both.

App registration to access Uber api

I have been trying to link Uber api to my app.
The User registration is successful but when i tried to create an app it says "Before you can create an application, we need to confirm your phone number."
How do i confirm my number to proceed further ?
Any input ?

To confirm your mobile number, just text the word go to 827-222.
If you don’t get a reply saying that your number was confirmed or the response is "Message blocking is active," your mobile service provider may be blocking you from texting our number. Give your provider a call to see if they will let you text 827-222.
Google Voice users may have to login to http://google.com/voice in order to text the word go to 827-222.
Still having trouble confirming your mobile number? We can help you at t.uber.com/support
If after doing this, and you still cannot create an application, please try to logout of the developer portal by visiting:
https://developer.uber.com/apps/logout
There was a caching issue where the developer portal didn't recognize when a mobile number was successfully confirmed.

Go to this link on uber Help page and enter your mobile number. Somebody from their support will get back to you over email. Explain the issue to them and they will resolve it for you from their internal tool/backend system. This is how I resolved it for myself.

Android Installs Not Showing on Facebook Developer Insights

So I have an iOS and Android phone application that also has a Facebook application which enables users to share information. Every time someone downloads the application my analytics should show installs both iOS and Android, unfortunately it is just iOS, I'm not sure how to get it to register the Android installs, can anyone help?

This is very easy to do, just from looking at the documentation, please check there next time. Here is what you need to do:
On your very first Activity add the following to your onCreate, As you can see below it requires a context and maybe the application ID.
AppEventsLogger.activateApp(this, yourAppIdHere);
https://developers.facebook.com/docs/reference/android/current/class/AppEventsLogger/

Can a android device start giving null value for device id?

I have an app on the market. When you start playing your device id is linked to your account so you don't have to log in manually. For some time now a few people had a problem. They started logging in into different accounts. What seems to be the problem is that some devices give a null value when asked for device id. With a few accounts with a null device id, people were logging into different accounts.
I read that some devices will do that. But it seems that there was no problem during account creation and then playing for a while.
I know this is not the best method and google discourages using device ids since they can change on fabric reset.
Can a device for some reason stop giving its id(besides the fabric reset)?
Anyone know of a different way to identify the user with out him needing to put in a login or password?

Yes some phones have bugs in them where they will return NULL for Android ID. I think if you want to continue to use them you'll always need a way to tie that handset to an account, email, username. That way if the Android ID is unrecognized they could login using their email or username, and password to associate them again. You'll always have issues where someone buys a new phone and needs a way recover their account if you don't.
A better option is every Android phone is attached to a Google account. And using the AccountManager class you can use those credentials to authenticate to your software automatically and the user doesn't have to enter username/password. And you'e centralized their identity. Also with this method you don't require the extra permissions to read data that has potential security issues too.

You could create a random UUID after the user has installed your app.
Do not use hardware ids, because not every type of hardware is found in every type of Android device. Another reason not to use them is, if someone sells his phone, the user changes but the device id not! This has serious privacy and usability implications you do not want to have.
See the talk Android Protips (from google io 2011). Tune in at 15:00 to see more reasons and a detailed descriptions on how to use random UUIDs for your usecase.

I am facing the same problem In my case when first install the app it is giving null id . but after that it is giving me all three IMEI, ANDROID_ID and deviceID.
BTW, you can find the ways to identify the devices here
http://innovator.samsungmobile.com/cms/cnts/knowledge.detail.view.do?platformId=1&cntsId=9640

Also some research prototypes try to prevent phones from collecting this information.