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.
Related
In my app, SIP registration was successfully done,but when i am checking in my phone weather account is added or not, account is added but when i am clicking on that then popup appears with two option:
1.Close Profile
2.Cancel
So there may be account not successfully added.So please suggest me to solve this issue.Thank you.
Have a look at this post and this post if you're okay w/launching the native sip-settings dialog and then reading the settings out afterwards. You could also do as another user suggested and use a service.
See the official Android SIP API for the latest, in case such an option has become available.
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.
I think this may not be the right question for this forum, but I could not think of where else to post it.
However, here goes. I am creating a dating app in android. One of the major hurdles I am facing is user authentication and verification.
Put simply, how do I ensure that a user is who he/she really says he is? How do I prevent, or reduce people creating fake profiles on the app? One way to do this would be to force the user to connect with his facebook account, but again, fake facebook profiles can be created.
Is there any other good method to ensure user verification?
The best way I can think of, although not fool proof, would be when the user creates an account it sends them an email where they need to click a link. Clicking the link can ask for some confirmation of something, such as their chosen username and or the first name and last name etc. If they fill in this information from the email, they're probably legit and you can mark the account as active within the database. If after x number of days delete any accounts that have not been verified.
I integrated admob in android application and I reached threshold. it displays a message that, Your payments are currently on hold because you have not verified your address is there any way instead of waiting for many weeks to receive PIN from admob for address verification?
I have noticed that for adsense, https://support.google.com/adsense/contact/id_verification?hl=en to submit address proof to save many weeks to recieve PIN.
Similarly for admob, is there any link to attach address proof? or I want to wait for many weeks to receive PIN?
After the failure of 3rd application for PIN, admob will give you a link automatically for uploading proof to verify your identity.After that, you will be identified in 24 hours.
google is not providing link for uploading proof and there help link is not available.
I like to implement Refer a Friend functionality in my mobile application (Android and iPhone).
User "A" will refer my mobile contacts via SMS (Referred user "B"). And if "B" install my referred application or the referred content, "A" will earn some reward points.
This is my scenario. Suggest me.
Thanks in advance.
I used Google Analytics Campaign to implement this scenario.
Another way to do this is to generate unique links for all your users, that they can then send out to their contacts.
Let's say User A shares a link with User B. When User B clicks on the link to get your app, rather than immediately redirecting to the App Store, you can make a call to your backend, with the goal being to create a digital fingerprint. Your backend can record the digital fingerprint then do a 301, 304 or 307 redirect to the App Store.
To create the digital fingerprint, your backend can then make a browser-based digital fingerprint including:
1. IP address
2. OS
3. OS version
(These can be grabbed from the request headers).
--
Later when the user opens your app, you should send up the same 3 things, IP, OS and OS version. If they match and are close time-wise, you know that they came from this click from User A's link! Then you can give User A a reward and thank him for getting User B to download the app. This is what we do at Branch Metrics, where I work. We also leverage a browser cookie that works across apps, so that we don't need to rely on fingerprinting except for the very first time we see a user in any of our apps.
You should also think about preventing fraud. You should prevent User A from referring himself, you should prevent User A from referring User B over and over, etc. This is something we work on everyday as well. Definitely spend time on fraud prevention unless you really don't care about giving out duplicate rewards to the same user. Please leave a comment if you'd like more info.