Skip to content
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

Failing to build IOS app #58

Open
ManindraDeMel opened this issue Aug 27, 2024 · 13 comments
Open

Failing to build IOS app #58

ManindraDeMel opened this issue Aug 27, 2024 · 13 comments

Comments

@ManindraDeMel
Copy link

ManindraDeMel commented Aug 27, 2024

Failed to build iOS app
Semantic Issue (Xcode): 'init' is unavailable
/Users/XXXX/.pub-cache/hosted/pub.dev/libphonenumber-2.0.2/ios/Classes/LibphonenumberPlugin.m:15:52

No Issues with Android build

@khalilyamoun
Copy link

Our team is experiencing the same exact issue.

@Nahrawene-ben-hmida
Copy link

I also had the same issue with building the iOS app using libphonenumber 2.0.2

@azizsoule
Copy link

azizsoule commented Aug 27, 2024

Hello ! Our team experienced the same issue.
The underlying ios library used by this plugin has been updated yesterday from version 0.9.9 to 1.2.0 (1.2.0 seems to contains breaking change). See libPhoneNumber-iOS cocoapods page.
As a workaround to fix the issue, you can pin the dependency to version 0.9.9 to keep your process working.
You can do that by adding this line at the end of your flutter project Podfile in the ios folder :
pod 'libPhoneNumber-iOS', '0.9.9'

@azizsoule
Copy link

I have also submitted a fix to the plugin directly but as i said in the PR description, we should implement a newer version version of the plugin using the latest version of libPhoneNumber-iOS.
Link tot the PR

@brunosp15
Copy link

Same problem here. Since yesterday my github action API is breaking.
iOS because of libphonenumber and android because of camera_android_camerax.

@unknownaloy
Copy link

Hello ! Our team experienced the same issue. The underlying ios library used by this plugin has been updated yesterday from version 0.9.9 to 1.2.0 (1.2.0 seems to contains breaking change). See libPhoneNumber-iOS cocoapods page. As a workaround to fix the issue, you can pin the dependency to version 0.9.9 to keep your process working. You can do that by adding this line at the end of your flutter project Podfile in the ios folder : pod 'libPhoneNumber-iOS', '0.9.9'

I've tried doing this at the end of my Podfile I added the line

end
pod 'libPhoneNumber-iOS', '0.9.9'

This is the version I'm using on my pubspec.yaml

libphonenumber: ^2.0.2

@CarlosMoraRoa
Copy link

Hello ! Our team experienced the same issue. The underlying ios library used by this plugin has been updated yesterday from version 0.9.9 to 1.2.0 (1.2.0 seems to contains breaking change). See libPhoneNumber-iOS cocoapods page. As a workaround to fix the issue, you can pin the dependency to version 0.9.9 to keep your process working. You can do that by adding this line at the end of your flutter project Podfile in the ios folder : pod 'libPhoneNumber-iOS', '0.9.9'

This solution worked for me!

@azizsoule
Copy link

Hello ! Our team experienced the same issue. The underlying ios library used by this plugin has been updated yesterday from version 0.9.9 to 1.2.0 (1.2.0 seems to contains breaking change). See libPhoneNumber-iOS cocoapods page. As a workaround to fix the issue, you can pin the dependency to version 0.9.9 to keep your process working. You can do that by adding this line at the end of your flutter project Podfile in the ios folder : pod 'libPhoneNumber-iOS', '0.9.9'

I've tried doing this at the end of my Podfile I added the line

end pod 'libPhoneNumber-iOS', '0.9.9'

This is the version I'm using on my pubspec.yaml

libphonenumber: ^2.0.2

Did it work ?

@unknownaloy
Copy link

Hello ! Our team experienced the same issue. The underlying ios library used by this plugin has been updated yesterday from version 0.9.9 to 1.2.0 (1.2.0 seems to contains breaking change). See libPhoneNumber-iOS cocoapods page. As a workaround to fix the issue, you can pin the dependency to version 0.9.9 to keep your process working. You can do that by adding this line at the end of your flutter project Podfile in the ios folder : pod 'libPhoneNumber-iOS', '0.9.9'

I've tried doing this at the end of my Podfile I added the line
end pod 'libPhoneNumber-iOS', '0.9.9'
This is the version I'm using on my pubspec.yaml
libphonenumber: ^2.0.2

Did it work ?

No, it didn't work for me

I'm also running flutter 3.24.1

@azizsoule
Copy link

Hello ! Our team experienced the same issue. The underlying ios library used by this plugin has been updated yesterday from version 0.9.9 to 1.2.0 (1.2.0 seems to contains breaking change). See libPhoneNumber-iOS cocoapods page. As a workaround to fix the issue, you can pin the dependency to version 0.9.9 to keep your process working. You can do that by adding this line at the end of your flutter project Podfile in the ios folder : pod 'libPhoneNumber-iOS', '0.9.9'

I've tried doing this at the end of my Podfile I added the line
end pod 'libPhoneNumber-iOS', '0.9.9'
This is the version I'm using on my pubspec.yaml
libphonenumber: ^2.0.2

Did it work ?

No, it didn't work for me

I'm also running flutter 3.24.1

Did you tried to run pod install --repo-update after you added the line to your Podfile ?

@ManindraDeMel
Copy link
Author

ManindraDeMel commented Aug 28, 2024

Hi everyone, i found it easier to just switch to the more actively maintained https://pub.dev/packages/flutter_libphonenumber (flutter_libphonenumber). Its a reasonably simple migration. They mention this exact issue in their changelong

@unknownaloy
Copy link

pod install --repo-update

My problem is from somewhere else, and I am getting other errors. Thanks for the help

@azizsoule
Copy link

Hi everyone, i found it easier to just switch to the more actively maintained https://pub.dev/packages/flutter_libphonenumber (flutter_libphonenumber). Its a reasonably simple migration. They mention this exact issue in their changelong

I agree with you @ManindraDeMel. It's another solution 💙 !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants