Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
I have following setup: flutter plugin with an example app the plugin depends on a native library (flutter_plugin.podspec contains s.dependency 'native-lib', '0.1.0') for local development I pull ...
#7: Post edited
by
Someone
·
2020-10-20T08:52:31Z (about 4 years ago)
- I have following setup:
- 1. flutter plugin with an example app
- 2. the plugin depends on a native library (`flutter_plugin.podspec` contains `s.dependency 'native-lib', '0.1.0'`)
- 3. for local development I pull in the native library in the example app `Podfile` via `pod 'native-lib', :path => '../../dependencies/native-lib/ios/'`
4. the local `native-lib.podspec` sets `s.version = '0.11.0-dev'`- With this setup I would expect `pods install` to pull in the local lib. Instead, it says:
- ```
- [!] CocoaPods could not find compatible versions for pod "native-lib":
- In Podfile:
- native-lib (from `../../dependencies/native-lib/ios/`)
- flutter_plugin (from `.symlinks/plugins/flutter_plugin/ios`) was resolved to 0.0.1, which depends on
- native-lib (= 0.1.0,)
- ```
- Not even specifying `s.dependency 'native-lib', '0.1.0', '0.1.0-dev'` (or `s.dependency 'native-lib', '0.1.0-dev', '0.1.0'`) in the `.podspec` works. What does work is using `0.1.0-dev` but that will probably break when the real `0.1.0` is offered.
- **Why does the Podfile/podspec not accept 0.1.0-dev when the requirement is 0.1.0?**
- The [Podfile documentation](https://guides.cocoapods.org/syntax/podfile.html#pod) says:
- > ~> 0.1.3-beta.0 Beta and release versions for 0.1.3, release versions up to 0.2 excluding 0.2. Components separated by a dash (-) will not be considered for the version requirement.
- But even specifying `~> 0.1.0` as required version does not pick up `0.1.0-dev`.
- The [podspec documentation](https://guides.cocoapods.org/syntax/podspec.html#dependency) does not mention dash suffixes.
- I have following setup:
- 1. flutter plugin with an example app
- 2. the plugin depends on a native library (`flutter_plugin.podspec` contains `s.dependency 'native-lib', '0.1.0'`)
- 3. for local development I pull in the native library in the example app `Podfile` via `pod 'native-lib', :path => '../../dependencies/native-lib/ios/'`
- 4. the local `native-lib.podspec` sets `s.version = '0.1.0-dev'`
- With this setup I would expect `pods install` to pull in the local lib. Instead, it says:
- ```
- [!] CocoaPods could not find compatible versions for pod "native-lib":
- In Podfile:
- native-lib (from `../../dependencies/native-lib/ios/`)
- flutter_plugin (from `.symlinks/plugins/flutter_plugin/ios`) was resolved to 0.0.1, which depends on
- native-lib (= 0.1.0,)
- ```
- Not even specifying `s.dependency 'native-lib', '0.1.0', '0.1.0-dev'` (or `s.dependency 'native-lib', '0.1.0-dev', '0.1.0'`) in the `.podspec` works. What does work is using `0.1.0-dev` but that will probably break when the real `0.1.0` is offered.
- **Why does the Podfile/podspec not accept 0.1.0-dev when the requirement is 0.1.0?**
- The [Podfile documentation](https://guides.cocoapods.org/syntax/podfile.html#pod) says:
- > ~> 0.1.3-beta.0 Beta and release versions for 0.1.3, release versions up to 0.2 excluding 0.2. Components separated by a dash (-) will not be considered for the version requirement.
- But even specifying `~> 0.1.0` as required version does not pick up `0.1.0-dev`.
- The [podspec documentation](https://guides.cocoapods.org/syntax/podspec.html#dependency) does not mention dash suffixes.
#6: Post edited
by
Someone
·
2020-10-20T08:52:05Z (about 4 years ago)
- I have following setup:
- 1. flutter plugin with an example app
- 2. the plugin depends on a native library (`flutter_plugin.podspec` contains `s.dependency 'native-lib', '0.1.0'`)
3. for local development I pull in the native library in the example app `Podfile` via `pod 'an-scan-native', :path => '../../dependencies/an-scan-native/ios/'`4. the local library has version `0.1.0-dev`- With this setup I would expect `pods install` to pull in the local lib. Instead, it says:
- ```
- [!] CocoaPods could not find compatible versions for pod "native-lib":
- In Podfile:
- native-lib (from `../../dependencies/native-lib/ios/`)
- flutter_plugin (from `.symlinks/plugins/flutter_plugin/ios`) was resolved to 0.0.1, which depends on
- native-lib (= 0.1.0,)
- ```
- Not even specifying `s.dependency 'native-lib', '0.1.0', '0.1.0-dev'` (or `s.dependency 'native-lib', '0.1.0-dev', '0.1.0'`) in the `.podspec` works. What does work is using `0.1.0-dev` but that will probably break when the real `0.1.0` is offered.
- **Why does the Podfile/podspec not accept 0.1.0-dev when the requirement is 0.1.0?**
- The [Podfile documentation](https://guides.cocoapods.org/syntax/podfile.html#pod) says:
- > ~> 0.1.3-beta.0 Beta and release versions for 0.1.3, release versions up to 0.2 excluding 0.2. Components separated by a dash (-) will not be considered for the version requirement.
- But even specifying `~> 0.1.0` as required version does not pick up `0.1.0-dev`.
- The [podspec documentation](https://guides.cocoapods.org/syntax/podspec.html#dependency) does not mention dash suffixes.
- I have following setup:
- 1. flutter plugin with an example app
- 2. the plugin depends on a native library (`flutter_plugin.podspec` contains `s.dependency 'native-lib', '0.1.0'`)
- 3. for local development I pull in the native library in the example app `Podfile` via `pod 'native-lib', :path => '../../dependencies/native-lib/ios/'`
- 4. the local `native-lib.podspec` sets `s.version = '0.11.0-dev'`
- With this setup I would expect `pods install` to pull in the local lib. Instead, it says:
- ```
- [!] CocoaPods could not find compatible versions for pod "native-lib":
- In Podfile:
- native-lib (from `../../dependencies/native-lib/ios/`)
- flutter_plugin (from `.symlinks/plugins/flutter_plugin/ios`) was resolved to 0.0.1, which depends on
- native-lib (= 0.1.0,)
- ```
- Not even specifying `s.dependency 'native-lib', '0.1.0', '0.1.0-dev'` (or `s.dependency 'native-lib', '0.1.0-dev', '0.1.0'`) in the `.podspec` works. What does work is using `0.1.0-dev` but that will probably break when the real `0.1.0` is offered.
- **Why does the Podfile/podspec not accept 0.1.0-dev when the requirement is 0.1.0?**
- The [Podfile documentation](https://guides.cocoapods.org/syntax/podfile.html#pod) says:
- > ~> 0.1.3-beta.0 Beta and release versions for 0.1.3, release versions up to 0.2 excluding 0.2. Components separated by a dash (-) will not be considered for the version requirement.
- But even specifying `~> 0.1.0` as required version does not pick up `0.1.0-dev`.
- The [podspec documentation](https://guides.cocoapods.org/syntax/podspec.html#dependency) does not mention dash suffixes.
#5: Post edited
by
Someone
·
2020-10-20T08:46:59Z (about 4 years ago)
- I have following setup:
- 1. flutter plugin with an example app
- 2. the plugin depends on a native library (`flutter_plugin.podspec` contains `s.dependency 'native-lib', '0.1.0'`)
- 3. for local development I pull in the native library in the example app `Podfile` via `pod 'an-scan-native', :path => '../../dependencies/an-scan-native/ios/'`
- 4. the local library has version `0.1.0-dev`
- With this setup I would expect `pods install` to pull in the local lib. Instead, it says:
- ```
- [!] CocoaPods could not find compatible versions for pod "native-lib":
- In Podfile:
- native-lib (from `../../dependencies/native-lib/ios/`)
- flutter_plugin (from `.symlinks/plugins/flutter_plugin/ios`) was resolved to 0.0.1, which depends on
- native-lib (= 0.1.0,)
- ```
Not even specifying `s.dependency 'native-lib', '0.1.0', '0.1.0-dev'` (or `s.dependency 'native-lib', '0.1.0-dev', '0.1.0'` in the `.podspec` works. What does work is using `0.1.0-dev`.- **Why does the Podfile/podspec not accept 0.1.0-dev when the requirement is 0.1.0?**
- The [Podfile documentation](https://guides.cocoapods.org/syntax/podfile.html#pod) says:
- > ~> 0.1.3-beta.0 Beta and release versions for 0.1.3, release versions up to 0.2 excluding 0.2. Components separated by a dash (-) will not be considered for the version requirement.
- But even specifying `~> 0.1.0` as required version does not pick up `0.1.0-dev`.
- The [podspec documentation](https://guides.cocoapods.org/syntax/podspec.html#dependency) does not mention dash suffixes.
- I have following setup:
- 1. flutter plugin with an example app
- 2. the plugin depends on a native library (`flutter_plugin.podspec` contains `s.dependency 'native-lib', '0.1.0'`)
- 3. for local development I pull in the native library in the example app `Podfile` via `pod 'an-scan-native', :path => '../../dependencies/an-scan-native/ios/'`
- 4. the local library has version `0.1.0-dev`
- With this setup I would expect `pods install` to pull in the local lib. Instead, it says:
- ```
- [!] CocoaPods could not find compatible versions for pod "native-lib":
- In Podfile:
- native-lib (from `../../dependencies/native-lib/ios/`)
- flutter_plugin (from `.symlinks/plugins/flutter_plugin/ios`) was resolved to 0.0.1, which depends on
- native-lib (= 0.1.0,)
- ```
- Not even specifying `s.dependency 'native-lib', '0.1.0', '0.1.0-dev'` (or `s.dependency 'native-lib', '0.1.0-dev', '0.1.0'`) in the `.podspec` works. What does work is using `0.1.0-dev` but that will probably break when the real `0.1.0` is offered.
- **Why does the Podfile/podspec not accept 0.1.0-dev when the requirement is 0.1.0?**
- The [Podfile documentation](https://guides.cocoapods.org/syntax/podfile.html#pod) says:
- > ~> 0.1.3-beta.0 Beta and release versions for 0.1.3, release versions up to 0.2 excluding 0.2. Components separated by a dash (-) will not be considered for the version requirement.
- But even specifying `~> 0.1.0` as required version does not pick up `0.1.0-dev`.
- The [podspec documentation](https://guides.cocoapods.org/syntax/podspec.html#dependency) does not mention dash suffixes.
#4: Post edited
by
Someone
·
2020-10-20T08:45:45Z (about 4 years ago)
- I have following setup:
- 1. flutter plugin with an example app
- 2. the plugin depends on a native library (`flutter_plugin.podspec` contains `s.dependency 'native-lib', '0.1.0'`)
- 3. for local development I pull in the native library in the example app `Podfile` via `pod 'an-scan-native', :path => '../../dependencies/an-scan-native/ios/'`
- 4. the local library has version `0.1.0-dev`
- With this setup I would expect `pods install` to pull in the local lib. Instead, it says:
- ```
- [!] CocoaPods could not find compatible versions for pod "native-lib":
- In Podfile:
- native-lib (from `../../dependencies/native-lib/ios/`)
- flutter_plugin (from `.symlinks/plugins/flutter_plugin/ios`) was resolved to 0.0.1, which depends on
- native-lib (= 0.1.0,)
- ```
Specifying `s.dependency 'native-lib', '0.1.0', '0.1.0-dev'` the `.podspec` works but I'd like to avoid this being committed to consumers and having to specify the version twice.- **Why does the Podfile/podspec not accept 0.1.0-dev when the requirement is 0.1.0?**
- The [Podfile documentation](https://guides.cocoapods.org/syntax/podfile.html#pod) says:
- > ~> 0.1.3-beta.0 Beta and release versions for 0.1.3, release versions up to 0.2 excluding 0.2. Components separated by a dash (-) will not be considered for the version requirement.
- But even specifying `~> 0.1.0` as required version does not pick up `0.1.0-dev`.
- The [podspec documentation](https://guides.cocoapods.org/syntax/podspec.html#dependency) does not mention dash suffixes.
- I have following setup:
- 1. flutter plugin with an example app
- 2. the plugin depends on a native library (`flutter_plugin.podspec` contains `s.dependency 'native-lib', '0.1.0'`)
- 3. for local development I pull in the native library in the example app `Podfile` via `pod 'an-scan-native', :path => '../../dependencies/an-scan-native/ios/'`
- 4. the local library has version `0.1.0-dev`
- With this setup I would expect `pods install` to pull in the local lib. Instead, it says:
- ```
- [!] CocoaPods could not find compatible versions for pod "native-lib":
- In Podfile:
- native-lib (from `../../dependencies/native-lib/ios/`)
- flutter_plugin (from `.symlinks/plugins/flutter_plugin/ios`) was resolved to 0.0.1, which depends on
- native-lib (= 0.1.0,)
- ```
- Not even specifying `s.dependency 'native-lib', '0.1.0', '0.1.0-dev'` (or `s.dependency 'native-lib', '0.1.0-dev', '0.1.0'` in the `.podspec` works. What does work is using `0.1.0-dev`.
- **Why does the Podfile/podspec not accept 0.1.0-dev when the requirement is 0.1.0?**
- The [Podfile documentation](https://guides.cocoapods.org/syntax/podfile.html#pod) says:
- > ~> 0.1.3-beta.0 Beta and release versions for 0.1.3, release versions up to 0.2 excluding 0.2. Components separated by a dash (-) will not be considered for the version requirement.
- But even specifying `~> 0.1.0` as required version does not pick up `0.1.0-dev`.
- The [podspec documentation](https://guides.cocoapods.org/syntax/podspec.html#dependency) does not mention dash suffixes.
#3: Post edited
by
Someone
·
2020-10-20T08:34:22Z (about 4 years ago)
pod x.y.z-dev not accepted for required version x.y.z (without -dev suffix)
- pod 0.1.0-dev not accepted for required version 0.1.0 (without -dev suffix)
#2: Post edited
by
Someone
·
2020-10-20T08:33:53Z (about 4 years ago)
Local path pod version x.y.z-dev not accepted for dependency version x.y.z (without -dev suffix)
- pod x.y.z-dev not accepted for required version x.y.z (without -dev suffix)
#1: Initial revision
by
Someone
·
2020-10-20T08:32:56Z (about 4 years ago)
Local path pod version x.y.z-dev not accepted for dependency version x.y.z (without -dev suffix)
I have following setup:
1. flutter plugin with an example app
2. the plugin depends on a native library (`flutter_plugin.podspec` contains `s.dependency 'native-lib', '0.1.0'`)
3. for local development I pull in the native library in the example app `Podfile` via `pod 'an-scan-native', :path => '../../dependencies/an-scan-native/ios/'`
4. the local library has version `0.1.0-dev`
With this setup I would expect `pods install` to pull in the local lib. Instead, it says:
```
[!] CocoaPods could not find compatible versions for pod "native-lib":
In Podfile:
native-lib (from `../../dependencies/native-lib/ios/`)
flutter_plugin (from `.symlinks/plugins/flutter_plugin/ios`) was resolved to 0.0.1, which depends on
native-lib (= 0.1.0,)
```
Specifying `s.dependency 'native-lib', '0.1.0', '0.1.0-dev'` the `.podspec` works but I'd like to avoid this being committed to consumers and having to specify the version twice.
**Why does the Podfile/podspec not accept 0.1.0-dev when the requirement is 0.1.0?**
The [Podfile documentation](https://guides.cocoapods.org/syntax/podfile.html#pod) says:
> ~> 0.1.3-beta.0 Beta and release versions for 0.1.3, release versions up to 0.2 excluding 0.2. Components separated by a dash (-) will not be considered for the version requirement.
But even specifying `~> 0.1.0` as required version does not pick up `0.1.0-dev`.
The [podspec documentation](https://guides.cocoapods.org/syntax/podspec.html#dependency) does not mention dash suffixes.