I frequently get complaints from customers that they can't click the Allow button on the SSO screen of my app, that's based on the Facebook SDK. They say that it simply does not respond to clicks.
I have never been able to reproduce this problem. But it occasionally does have various errors when you do press the button, but trying a couple of times always ends up working.
Has anyone else encountered this issue? If I can't find a solution, I'm just going to have to permanently disable SSO.
Looks like a similar problem that I had. It was solved by not calling the Facebook app by default when going to authorize. To do so, simply add Facebook.FORCE_DIALOG_AUTH to the authorize parameters. A similar post with this answer can be found here.
I hope it helps =]
Related
I am building an Android app that signs in users to GitHub using OAuth. I followed the instructions here to do so. As the first part of the process, I sent users to the URL
https://github.com/login/oauth/authorize?scope=repo&client_id=MY_CLIENT_ID
However, when I sign in on my Android device, the Authorize xxxx button appears to be greyed out and I can't click it. Does anyone have a clue why this is? (Large screenshot below)
I think the button may not have been greyed out before, the first time I ran the app and signed in. However, I can't tell for sure because I was in a rush.
So, I pasted the link into Chrome on my computer and the OAuth process worked fine. I noticed the button was greyed out at first, but then became bright green. This got me wondering: was JavaScript enabled by default in the Android WebView? Sure enough, it wasn't. I found this answer which details how to enable JS. This was the key line that got everything working:
webView.getSettings().setJavaScriptEnabled(true);
I absolutely support what #james-ko said - JS has to be enabled for the WebView.
But sometimes it doesn't help. I found a little bit more info and would be happy to share it here.
Similar story - I have an app which is supposed to login the user with GitHub OAuth, everything works fine except the "Authorise" button - it just stays disabled whatever setting were applied is some cases.
Here is summary:
The button is always stays disabled on emulator with API 22 and 23 (I didn't try 24-27 though) regardless of settings and user behaviour.
It works well on emulator with API 28 and 29.
On the real device Pixel 3 (API 29), the button was disabled initially and nothing was happening for a while. But when I taped the screen twice in random places it got enabled. The app restarting reproduces the situation: initially disabled button --> tap on the screen --> button gets enabled.
Apparently some antifraud mechanism is involved.
But it gives kinda poor experience to the final user it looks like a bug in the app and there is not much what we can do about it :-/
I had the same problem in Safari, but I located a potential cause, the content security policy of the site was set to: script-src github.githubassets.com
im sending links via sms
like so:
hello, please click on http://example.com/Axcsy
some of the users call back with a problem that they cannot connect,
after inspected i realized that the link has been cut after they pressed on it.
so when they press it they get to http://example.com,
when they copy paste the entire link it works ofc...
is this a known issue or some setting that they changed?
I don't know of any issue that can cause this.
All i can think of is that they didnt click on it and just copy pasted it.
Note: it happened with only a few users (maybe 5 out of thousands), it has nothing to do with model type or android/IOS version (as far as i know, i checked with users that have the same model...)
if anyone has any clue why this is happening please answer,
thanks to anyone who replys
The users are probably using a text messaging app that causes this problem. Many users do not realize that Android can have different text messaging apps - and therefore don't realize they can change them.
Some of your users may have deliberately changed it and can tell you what app they are using, and they could then tell you so you can contact the developer. Even a provider's default app may have been created wrong or has a bug.
I'd like to receive an email whenever someone leaves a review for my Android app so that I can reply, if needed. I'm not seeing a setting for that in the Google play settings... Is this possible?
I know I could build something to programmatically check, but I'd prefer not to re-invent the wheel, and this seems like something that there would just be a setting for somewhere, or that would just happen automatically...
there is no official api unfortunately - but you can have a look at https://github.com/AndlyticsProject/andlytics - with this you can do what you want
I have never seen any such option either. I think using gsutil is your only option at this point.
This might be a weird question to ask.
But i want to make my application better.
I think i can find a solution here.
I am developing android apps..
It almost complete. What i am trying to figure it out is, how android error works.
I mean, i make an error so i will know when my apps crash, it will direct to some activity.
Like i delete an imagebutton in xml so my app will crash and unfortunately app has stopped will show up.
How do i direct to an activity after i click ok on that dialog ?
Is it possible to achieve something like that ?
Instead of crashing it would be better to implement try and catch where needed.
http://docs.oracle.com/javase/tutorial/essential/exceptions/try.html
This allows the app to softly deal with an error and continue. You could then redirect, but it would be better to just let it continue so the user wouldn't have to be interrupted.
I feel a little bit silly asking this, but I haven't been able to find any answers on my own. My Force Close dialog has a "Report" button. I think it's a great idea, and I wish everyone had it. At first, I thought it must be something I turned on without realizing it, but not only can't I find any setting that I might have touched, I also can't find any reference to this button existing on the Internet. I have a Droid, and I know 4 other people with Droids, and they say they don't have the option to report Force Closes. Am I special? Am I just missing something? The "report" button has been there for at least a few weeks now.
When I use the Report button, I get a screen with a "feedback" field and a checkbox for "Include system data". Below that , it says "Information from feedback reports will be shown to the developer of the application." Under that are Preview and Send buttons.
As a developer, I've never received one of these reports.
I'd try to send a report to myself, but it seemingly only shows the button for apps installed from the market, and I don't know of a way to crash my production app.
I suppose I could publish a simple crashing app just to try it out, but I thought I'd ask you folks first.
Edit:
You can view screenshots here: http://bentobin.com/crashReportImages/
This is a new feature of Android :)