Repository navigation
Fix linting when armv7 is included but i386 isn't - #8159
Conversation
|
Super agree validator is a tough class to write tests for...there are some though that print out the command so I think you might be able to copy-paste an existing one and verify the parameters passed are correct. |
|
Yeah, I found a test that is close at https://github.com/CocoaPods/CocoaPods/blob/master/spec/unit/validator_spec.rb#L622, but I couldn't figure out how to set or mock the architectures, like |
| when :ios | ||
| command += %w(CODE_SIGN_IDENTITY=- -sdk iphonesimulator) | ||
| command += Fourflusher::SimControl.new.destination(:oldest, 'iOS', deployment_target) | ||
| xcconfig = consumer.spec.attributes_hash['pod_target_xcconfig'] |
There was a problem hiding this comment.
You want to use consumer.pod_target_xcconfig here as it will take care of merging values etc. See https://github.com/CocoaPods/Core/blob/master/lib/cocoapods-core/specification/consumer.rb#L99-L102
|
@paulb777 needs a rebase and it should be OK |
|
Done. Thanks @dnkoutso! |
- Limit the supported podspec platform to iOS so tests don't run (and fail) for macOS. - Define the module by setting `DEFINES_MODULE` in the podspec. See [CocoaPod modular headers docs](http://blog.cocoapods.org/CocoaPods-1.5.0/). - Explicitly set `VALID_ARCHS` to architectures included in the Flutter universal binary. This is the CocoaPods-suggested workaround to prevent tests from running on the i386 simulator. See CocoaPods/CocoaPods#8159.
- Limit the supported podspec platform to iOS so tests don't run (and fail) for macOS. - Define the module by setting `DEFINES_MODULE` in the podspec. See [CocoaPod modular headers docs](http://blog.cocoapods.org/CocoaPods-1.5.0/). - Explicitly set `VALID_ARCHS` to architectures included in the Flutter universal binary. This is the CocoaPods-suggested workaround to prevent tests from running on the i386 simulator. See CocoaPods/CocoaPods#8159.
- Limit the supported podspec platform to iOS so tests don't run (and fail) for macOS. - Define the module by setting `DEFINES_MODULE` in the podspec. See [CocoaPod modular headers docs](http://blog.cocoapods.org/CocoaPods-1.5.0/). - Explicitly set `VALID_ARCHS` to architectures included in the Flutter universal binary. This is the CocoaPods-suggested workaround to prevent tests from running on the i386 simulator. See CocoaPods/CocoaPods#8159.
- Limit the supported podspec platform to iOS so tests don't run (and fail) for macOS. - Define the module by setting `DEFINES_MODULE` in the podspec. See [CocoaPod modular headers docs](http://blog.cocoapods.org/CocoaPods-1.5.0/). - Explicitly set `VALID_ARCHS` to architectures included in the Flutter universal binary. This is the CocoaPods-suggested workaround to prevent tests from running on the i386 simulator. See CocoaPods/CocoaPods#8159.
Fix #8129
I verified the bug report is fixed by this. If unit tests are needed, I'd appreciate tips on the right approach.