Testing Facebook integration prior to approval - android

I'd like to test a mobile app in development, which will use the Facebook API to log a user in and read mutual friends. However, from what I can tell, I can't use the API to log in a user unless the app is verified, but to verify the app, the review team will "need to test and verify [my] Facebook integration."
Considering (per my impression), I wouldn't be able to test my own integration before submitting it, I'm rather confused. I feel like this is a "chicken and the egg" thing, so I imagine I'm not understanding how this works correctly.
Could anyone please explain or point me to any resources that will? I've been searching endlessly on how to do this.
Thank you!

No need to wait for its approval. You'll need to create the app on itunesconnect.apple.com and then you'll be able to use the Apple ID you'll be given to test it.

Related

Facebook SDK Policy Issue - Android

I received a mail from Facebook:
Hi,
In working to create a great Platform experience for everyone, we ask developers to ensure the apps they build comply with our Platform Policies. Your app xxx (AppId: xxxxxxxxx) doesn't comply with the following:
Platform Policy 8.1: Verify that you have integrated Login correctly. Your app shouldn't crash or hang during the testing process.
During Login, your Android app is crashing or hanging excessively, creating a broken experience for people trying to use your app. To make sure this flow runs smoothly, check that you've integrated Facebook Login correctly. We recommend that you test Login on all integrations. If you have not already done so.
Please make the requested changes by 2019-08-08 at 12:00 PST.
Let us know when you've updated your app by replying to this email. If we do not hear back from you, your app will be subject to enforcement. If you have outstanding questions, respond here and we'll do our best to help.
Thanks,
Facebook
I have used the latest Facebook SDK in my app. Can anyone tell me how to deal with this situation. I really need some help right now.
Any help would be appreciated!

Android Dev. - I'm designing an app that will require sign-ups with a college email, but all i find are things for Google+. Any suggestions?

Like how I tried to effectively word in the title, my issue with Sign-ups and log-ins for my application is that it would work best with a college email, as it's an app designed for college campuses, but I can only find APIs and information regarding the Google+ sign-up that is everywhere.
For instance, an app like Kik does not require a Google+ sign-in and you can make your account however you like, but I've not found any information on how to go about creating a sign-in like that. The only substantial information regarding sign-ups/log-ins I've found are for the Google+ API.
The only other thing i thought of was using the Google+ sign-in to verify the person, and then having something in the settings to enter and save the college email for the uses it'll have.
Would any of you have thoughts on this? I'd prefer not to do the latter simply because it requires more for set-up of the app on the users part (which isn't ideal) to use it's full functionality, but I don't really see any other way of doing it at this point.

Facebook SDK - Getting all users that use the application

I don't know what you guys think, but I believe that the Facebook SDK documentation is very limited and doesn't explain very much; Luckily throughout the use of some videos I was able to set up most of the integration that I needed.
However my application doesn't interact with just Facebook friends. It interacts with anyone and everyone using the application. Meaning if Jim and Sally aren't facebook friends, they can still see each-others profile picture, age, and name.
I'm not asking for you guys to write this out for me, but a nudge in the right direction would be lovely, perhaps accompanied by a link.
There is no API to "get all App users", you would have to store each user in your own database. Of course you have to deal with users deauthorizing your App - you can do that with the "Deauthorize Callback URL" in the advanced settings of your App.

Loggin with G+ only for a comunity

I want to start a project where to use the app you need to be in a comunnity of G+.
SO I thought in different ways to do it:
Send registration and wait until and "admin" gives you permission
Use Loggin with G+, and then ask for validation
USe Loggin with G+, and see if you are in a concrete community, and let you log in or not.--> That solution will be perfect, but I don't know if is it possible to do.
So my question is:
Taking care that first 2 options are possible, I want to know if the third one can be done. And if is it possible, where can I find info? (I didn't see anything)
Thanks for all
There is not currently an API to identify what communities a Google+ user is in. There is an open feature request.

Removing Ad's with in-app-purchase

I'm searching for a tutorial or an explanation on how to remove advertisement in my application with in-app purchase?
I will put some ads with ad-mob in my app but I also want, that the user can disable the ads when he pays a little donation. Do you know a site or tutorial where I can find a step-by-step explanation how to do this?
Or do I need to publish 2 versions of my app? One with ads and one without ads for paying?
Don't use the SharedPreferences method because if the user flushes the app data or uninstalls/reinstalls your app their ad-free status will be lost.
A couple of ideas:
If your app has any kind of web based login or authorization, you can flag the user as having bought the ad free version by updating the web database's customer data and then disable ads in code following login and verification. This has the added benefit of following the user to new devices.
Use one of the several ways to get a unique device id, and store that in a web server database. On startup, query the DB to see if the device is ad-free. See Android Unique Device ID. This will only work for that particular device though.
The two apps approach is simple enough to get the job done too. :)
This presentation seems to explain an example and includes a link to source code at github:
http://gotocon.com/dl/2011/GeekNights/Tjen_penge_p%C3%A5_Android_ARH.pdf .
It stores the purchased upgrade at a sharedpreference.
However, I'm still looking for a more secure and robust solution that works out the use-case explained here:
http://vlingo-en.custhelp.com/app/answers/detail/a_id/1785/~/moving-in-app-purchase-(ad-removal)-to-new-android-phone/p/180

Categories

Resources