-
Notifications
You must be signed in to change notification settings - Fork 448
Errors like: Class TWTRScribeService is implemented in both ... #18
Comments
Same here. How can they release an extremely popular framework like this into production? Unbelievable. |
I have the same too.
Podfile.lock
Are there workarounds? |
I downgraded to the previous version. TwitterKit 3.3.0 had too many problems.
|
Thanks, I will. |
I am getting same warnings |
Same here |
I'm only importing TwitterKit 3.3.0 and getting the same errors; there must be some redundancies in TwitterKit and TwitterCore. Seems like TwitterKit automatically imports TwitterCore. |
same problems for me... any solution/workaround yet? |
Same problem here... couldn't find a solution... |
It is unbelievable that such an error still remains unresolved and no project manager has even replied in this thread. |
Same here with FirebaseUI |
@Asinox You should probably seek help for that one on a FirebaseUI repo, this is specifically for TwitterKit. I'm also having this issue after following the ReadMe instructions for Carthage. And I had just cleaned so much of the startup logs :( |
Same issue... |
Same Issue... |
Same here |
Same with using Firebase |
Downgrading to earlier version doesn't fix the issue. |
Seeing this same issue as well with the latest pod installation. |
Same issue here. |
Same logs here. |
Same here :( |
Same issue here, the app loads slower since |
Looks like this SDK is not maintained. Shame on Twitter. |
Same |
2 similar comments
Same |
Same |
Maybe there is a workaround for this CocoaPods/CocoaPods#7126 |
i'm facing same problem.. :( |
Same issue |
Same issue....... |
Same ;( |
We decided to remove Twitter (auth) from out project. |
Same here (Firebase UI) |
having the same issue, is there a fix yet ? |
What a terrible company discontinuing their Kit without any reason, start migrating now to something else. |
Issue still there. If no fix is coming it would be good to update the setup documentation to show using specific versions when installing the pods. |
Facing the issue which was working fine before updating new TwitterKit pods. Error: I also downgraded it by the following pod changes, even facing the same error. |
smindia1988: this is a different issue, Twitter now validates the callback URL and it must be registered in their backend. Read about it here: https://twittercommunity.com/t/action-required-sign-in-with-twitter-users-must-whitelist-callback-urls/105342 |
@pgutierrezcf : Thank for pointing me to correct required steps which was introduced just before few days and mandatory now. I got the solution from another link which is mandatory step: [Mandatory]
**For iOS:**
For Android: [ Note: Please replace your consumer key in place of words "CONSUMERKEY" in above format] Anyway thanks a lot :) |
Hi all, |
This still hasn't been fixed in the latest update.... |
Using latest TwitterCore (3.2.0) & TwitterKit (3.4.0). |
@p0tvin29 @littleylv They updated the installation instructions with a note that you must remove the TwitterShareExtensionUI references. Remove the framework, and go to the build phases for your targets and search for it there as well. https://github.com/twitter/twitter-kit-ios/wiki/Installation
|
@JacobJT I'm not seeing anything referencing to TwitterShareExtensionUI .. I checked build phases .. is there another location I should be looking? |
@p0tvin29 I had it in two places in the Build Phases. One was the Run Script, as an input file. The other I believe was Link Binary With Libraries, but I'm not 100% on that. |
@p0tvin29 @JacobJT I can't find any "TwitterShareExtensionUI" in build phases either. pod: 1.5.3 But when I downgrade to
there is a "TwitterShareExtensionUI" in "Build Phases" - "[CP] Copy Pod Resources" - "input files" |
Fixed by removing -framework "TwitterCore" from Pods-.debug.xcconfig and Pods-.release.xcconfig |
@BharatAgarSoftTech thanks.. this fixed mine. |
@p0tvin29 @BharatAgarSoftTech something to keep in mind - it will come back the next time you run a |
@taberrr You can fix this issue by using the following post install script:
|
@taberrr Thanks so much, working it around with this post install script works fine. In my case I was having a conflict with |
Same Issue guys ;(. Please resolve it asap. Its a major issue like big company. |
Is there any news about this topic for Swift 4.2 ? |
Error messages( but I faced to the related issue. if TWSession objects are invalid, check it. https://github.com/twitter/twitter-kit-ios/wiki/Installation
|
FIXED: - Mine was related to using the generic FirebaseUI instead of the specific method I intended to use: |
Bug Report
I'm getting lots of this on app startup.
Use TwitterKit framework in app. (using cocoapods, although the problem possibly might happen without cocoapods)
pod 'TwitterKit'
No logs like described.
iOS 11.2.1
iPhone 6s plus
Using TwitterCore (3.1.0)
Using TwitterKit (3.3.0)
The text was updated successfully, but these errors were encountered: