-
-
Notifications
You must be signed in to change notification settings - Fork 190
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Building for iOS fails #36
Comments
i'm facing the same thing on ios 15 |
@AhmedAbogameel @Waqar27324 I might have figured this out. Solution
For example, my post_install looks like this:
What I did in the fork What I've tested so far
I currently don't have an app that uses all capabilities of the pusher_client plugin, so I'm not able to test everything right now. But it seems to work perfectly fine now! @AhmedAbogameel @Waqar27324 could you test this solution in your project and let me know if it works for your projects as well? Anything I'm overlooking right now? If not, then I can submit a pull request for this package. |
I will definately try this later 🤞Thanks! |
definitely works @thijskuilman, only problem is I always got this error failed to connect to ws-ap1.pusher.com/XX.XXX.XX.XX (port 6001) from /:: (port 53350): connect failed: ETIMEDOUT (Connection timed out), I am expecting to connect to a defined domain not with pusher.com |
removing the cluster made me pass with this error |
have to drop it here tho, next thing after applying this is this error message [] nw_protocol_copy_ws_definition_block_invoke [C1.1:1] nw_ws_validate_server_response |
This works!! Thanks |
Fantastic |
I also facing same issue |
check this issue #39 there is a working workaround there |
HI @ragingallan I have tried all thing and at the last I end up with nw_protocol_copy_ws_definition_block_invoke [C1.1:1] nw_ws_validate_server_response error ... when I use V8 plugin...it working fine...but only in debug mode, In Archive build it making error like multiple command product with "Reachability" and "ReachabilityShift" frameWork . Now I'm totaly confused that what should I do? any solution? |
mmm., I ended up not using any package that has conflict with Reachability., here's the package that I used: |
#41 |
Any updates on this? |
@GauravCalidig @adham-ashraf77 Yes in my case I'm using below packages for "Reachability" and "ReachabilityShift" conflict I check all other packages who use this framework. Then I got "keyboard_visibility" plugin which had this conflict problem. then I remove this "Reachability" framework from keyboard_visibility.podspec file. this help me to get rid to build error
finally code is working fine. let me know if you need more help |
hi... If you working with laravel_echo and pusher client then you should have Sodium, second thing change IOS deployment target from 8.0 to 9.0 in above pods. |
I'm facing this error [] nw_protocol_copy_ws_definition_block_invoke [C18.1:1] nw_ws_validate_server_response |
after too many attempts. I did get some luck from this solution! but when I used this fork, I could not connect to the pusher. Then I reverted back to original plugin "pusher_client: ^2.0.0" , now my connections are stable and everything is working fine |
@ZakwanIbrahim3321 Did you make it worked in both android and ios? |
yes it's working on both android and iOS |
I changed this line |
@LakshithWithana
|
Steps to reproduce
flutter run
(I'm building for the iPhone 12 Pro Max simulator)Expected behavior
I'd expect the app to compile and run in the iOS simulator.
Actual behavior
I get the following error:
Output of
flutter doctor
:The text was updated successfully, but these errors were encountered: