Twitter callback URL does not fire #20
Comments
|
Sure. Note the funciton, signInFunc(), in the then clause: |
|
Thank you for the fast response .. I understand completely what you have written but unfortunately - we dont get to that stage .. i.e please see this snapshot :
|
|
Oh, I see. My next suggestion would be to view your logcat while attempting the login. Possibly it's complaining about the 'keys' used. As you know, my library package recently switched to an alternative plugin, flutter_login_facebook 0.1.2+3. If you don't see anything in the logcat, you may have to post an issue with the plugin author. I myself have had no such issue so far. Greg. |
|
@Andrious , I also have the same issue with your plugin. Twitter auth does not come back after you get successfully authenticated. Running the plugin outside of YOUR plugin works. Running your plugin that uses the TWITTER login plugin doesnt work. There is nothing wrong with keys/auth secret as next time I run the app - i'm authenticated and I can see the Twitter token. The issue appears to be with callback not working within your plugin. |
|
I forgot to mention, your plugin works (Twitter) when I use Android. Just doesnt work with iOS. I'm also using an Objective C iOS project. |
|
Ah! Interesting. @alexda12 , would that be the case with you as well? Are you having this issue in iOS and not Android? |
|
Hi - I'm trying to get google, facebook, twitter etc working with this Plugin and I'm having issues with the plugin. in iOS - after I type in my password and get a successful message from the relevant provider (say twitter) - nothing happens. I can only go back to my app if I press the DONE button at the top left corner of the device. Doing this actually CANCEL's the login flow. The issue only happens with iOS and works perfectly in Android. Please advise what I need to do to get this to work. |
|
Having compiled the authentication_app on my Macbook, the library plugin, Auth, worked like a charm. Note, I'm using the At this time, I can't explain the discrepancy. Why it works for most, but not others. Below are some of the other callbacks I used in the past. Again, it's to simply return to your running mobile app. There's something we're missing here. |
|
https://github.com/roughike/flutter_twitter_login/issues Lots of PRs and issues filed since the last commit of this project, which was back in 2018. The package being used on pub.dev is this fork: https://github.com/Maliffic/flutter_twitter_login, but the latter also hasn't been maintained since mid-2019. I suspect that there are quite a few things to get straightened out before this plugin can be realistically used in production. Most notably, roughike/flutter_twitter_login#34, without which Apple will reject your app submission. @Andrious, would you consider asking @roughike permission for maintaining the OG repo? |
|
@MaskyS, I will consider it. Ideally, I would like the original author to allow for pull requests. I will reach out to roughike (by an alternate means) and to others frankly and see if other managements can not be made. |
|
@alexda12, @MaskyS @bpaul7101 @ssbaval Yeah, I'm hitting a wall on this one. I went so far as go to the cache copy for the package, flutter_twitter, and changed the 'compileSdkVersion' value from 27 to 28. It seemed to have worked, but I will ask you all to try the same. I know it's a lot, but if it works, then we have something to work with and possibly fork the repo. and supply a fix. Go into your IDE and open up your project in question. You then open up 'Dart Packages' under 'External Libraries' and find flutter_twitter. Open up the file, flutter_twitter.dart, and then right-click on its path specified along the top. Right-click on the flutter_twitter folder to display its contents. You then click on the displayed folder, android. In that drop-down menu, click on the file build.gradle and open it up.
Change it the 'compileSdkVersion' value from 27 to 28. Close things up and try it. It's hoped this will help you. It's not a solution; it's a test. If it works, we'll fork it, and possibly some other changes to remove any deprecated API's.
|
|
Hi @Andrious , thanks for your latest post - but your comment is Android specific . If you recall from my original post #20 (comment), the issue I am having is with iOS and not Android. |
|
@alexda12, @MaskyS @bpaul7101 @ssbaval Oh boy. Forget that last post. Working on too many things here... Today, I'll see where we stand on this. |
|
@alexda12, @MaskyS @bpaul7101 @ssbaval Ok, let's see if we can't get a solution to this. Again, these are the callback url's I'm using. However, I want to get to the bottom of this I would suggest forking the repo. and see if you can get that to work. If you can, we're a little closer. First, here is the Note, retrieving this repository, you'll get all the 'iOS' files used, you'll be aware now of their version numbers. What I mean is, you'll get a lot of the ios/ folder content as well in the hope you'll succeed in running the example app and its Twitter login. I've even provided a 'Twitter app' in the file, GoogleServices-info.plist, to see if you can use Twitter login with that app. I'm supplying the 'podfile' that got the app working. Possibly you'll see something in there that makes the difference. In Podfile.lock, compare it to the file in your app and see if the version numbers of the similar files used in your app do not match: I've even given the list of Flutter packages used and their version numbers in the pubspec.lock file. Anything to help you out. I mean, it's pretty much the same listing above, but who knows, maybe there's something we missed. Lastly, I'll supply the |
|
I've completed some further testing, today. It's recommended, of course, to work with the channel, Flutter build channel releases It was a long and arduous exercise too. Every time I switched to another channel I would then issue a For example: |
|
Here is another posting of my latest tests. I've actually yet to go through my findings and see what may be the issue, I suspect you may have even moved on to an alternative. Again the channel, I decided to remove that file and have Xcode recreate it with the command, However, even in the channel, 'dev', the app will fail to build with this new podfile. If in the channel, The different packages and version numbers between the channel,
Lastly, is the long error message and warnings received when using the new podfile. It's been truncated a bit here, and it may not be useful to you in particular, |
|
@Andrious - Firstly, I want to commend you and say sincere thank you for the time and effort you are putting into trying to resolve this - i'm sure not just me but everyone here is appreciative of your efforts - hopefully we will establish why this isnt working soon ... Regarding what you have put here :
Thanks again... |
|
Please, what would be the status on this? |
|
@Andrious I have also experienced the issue with this plugin and have noted your PodFile issues and had exactly the same. If you were to run your plugin with 1.19.0-4.3.pre , you should not run into the issues mentioned above. The problems you are seeing in your PodFile is because Google decided to change the PodFile format apparently to make it easier to maintain. This means upgrading to flutter 1.20 will more than likely BREAK existing apps and you will experience severe pain trying to get your old PODFILE and dependencies working again. Additionally - all of Googles core plugins (Auth, Storage, Cloud Firestore, Google Sign-in etc) have moved over to this format so if you want the latest versions of these plugins you will have no choice but to go through the painful process of fixing regression and deprecation issues (Cloud Firestore has been re-written in terms of its TX codebase). Google didnt really think this through for existing Flutter based apps that were written pre 1.12 and relied heavily on old plugins that have not updated to this new format. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Thanks for the plugin. I see you have updated both Facebook and twitter to handle the deprecated API'S. In using TWITTER - I get my TWITTER login showing but after I authenticate - my app is not returned to.
I just get stuck on :
Twitter has been configured properly and I have these callbacks :
info.plist has also been setup with the twitter key in UrlSchemes :
My project is an OBJ-C iOS project using default AppDelegate.
Is there anything else that needs to be configured to get the twitter callback redirecting back to my app with your plugin ?
The text was updated successfully, but these errors were encountered: