Twitter sign up works on laptop, fails on mobile

csf

I'd like to setup the Twitter extension so people can login that way. I realize I need to create a new key, but a couple of questions:

The "Callback URL" field is optional in the Twitter form, but I see some Flarum admins have trouble if they don't add a URL here. What should this URL be if not the "Website" URL? (E.g. these instructions for GitHub say it should be the app website URL plus this on the end: /login/callback.)
Twitter is saying I need to add a phone number to my twitter account before I can create an app, which I'm not thrilled about doing. Why does it need the phone number? (By comparison, GitHub does not require a phone number.) Can I just give it a fake? ?

Dominion

I'm not sure about the phone number, but I suspect they want you to use two-factor authentication.

If that's the case, then a fake phone number is probably not a good idea. I'm just guessing, though.

csf

If 2-factor is the reason, then yeah, probably not a good idea, since you wouldn't get the security codes via text message.

csf

I'm not sure what 2-factor has to do with an app key though, where a login for everyone else is the focus. Either way, I guess I have no choice if I want to use the extension.

datitisev

csf I would guess it is to protect your app, aka not let other people into your account so easily because they could break your login.

Digital

Please see this post:

froginthevalleyformerly, Twitter Staff Feb '14

First off, we are really sorry about the troubles you might have with app registration. We are experimenting with new requirements for application creation to reduce abusive uses of the platform.
If you're unfortunately unable to meet these requirements, please use the last form option on https://support.twitter.com/forms/platform 2.7k and a member of our platform operations team will assist you.

Source: https://twittercommunity.com/t/how-to-create-an-app-without-mobile/21135/17

csf

Thanks, Digital. Seems a lot of people feel as I do. It's stupid. It's probably part of Twitter's "We support the NSA" policy. ?

jordanjay29

Two factor auth is just a good idea in general, IMHO. Not all TFA is implemented well (what happens when your phone gets stolen? Is there an alternate TFA method? Most don't have more than one.) but at minimum it stops random people from doing much of anything with your username/password if they get ahold of it.

As far as Twitter's policy goes, it's probably more interested in making sure people who make apps don't get compromised by weak passwords and see potentially thousands of users hurt. Twitter could potentially be liable for damages that occurred from that. So this is protecting them as much as you.

csf

I've created the Twitter key and secret and added it to the Twitter signup extension's settings, but I'm getting reports from beta testers that they are having problems. They're getting an error screen with this at the top...

League\OAuth1\Client\Credentials...
CredentialsException
Received HTTP status code [401] with message “<?xml version=“1.0” encoding=“UTF-8”?><hash><error><Desktop applications only support the oauth_callback value...

That's all they gave me, so I don't know what follows those ellipses. But there's a problem somewhere. What should I do? Dashboard says I'm running 0.1.0-beta.5.

csf

Btw, just to mention this now because I'm getting tired of it... every time I try to post in this forum, I have to do it twice because I get a red error on the first attempt saying "Oops... something went wrong. Please reload the page and try again." If I close that and try again it works, but that shouldn't be happening at all, ideally speaking.

We also see these in our boards on occasion and it confuses my non-tech users.

Dominion

csf Please create a separate discussion concerning your "Oops" message problem, as that really needs to be dealt with separately from the OAuth issue. I have seen that message while posting on this site, but only very rarely. If you're seeing it frequently, we'll probably need more information to pin down the reason for that.

Digital

Following up what @Dominion suggested:

@csf please continue the discussion about "Oops error" here: https://discuss.flarum.org/d/2914-oops-something-went-wrong-error

csf

I think there's more feedback and high-fives about my wayward forum use than about my problem. Can anyone address the issue? I mean, I gave Twitter my phone number... It would be nice if the extension worked.

Dominion

csf Perhaps this discussion will offer some clues ... Have you tried clearing the Flarum cache?

csf

Dominion Have you tried clearing the Flarum cache?

I will try that, thanks. Is this what you mean? https://discuss.flarum.org/d/2160-how-to-flush-cache/2

Dominion

I believe so ... this issue may also hold some useful information.

csf

Regarding the storage/cache directory... mine has folders in it with names like "61" and "c3", and they have similarly named items in them. Do we clear out all of those things leaving an entirely empty /cache directory or is it just the .js files in the root of /cache?

And here is a screenshot of the issues people keep seeing when trying to Sign up with Twitter extension...

I've tried it with and without a callback URL, but it doesn't change anything.

By comparison, I have the GitHub sign-up working, and all I needed to do there was remove the faulty callback URL and leave the field blank. After that no issues. Twitter is not playing so well.

Dominion

Going by the first post by @luceos in the issue I linked, it looks like all the subdirectories should go as well.

csf

Thanks. So in general, I should just remove all those weird .js and .css files whenever I see them in /assets and storage/cache?

Are there dev plans to make it so that junk doesn't pile up to begin with? I've never seen an app do that before with .js and .css files, but I'm not a dev. ? It's a little confusing when working with repos and syncing locally, because those files keep coming and going.