Azur Haljeta
11/28/2020, 1:47 PMframeworkName
specified in cocoapods{}
is ignored when building the .podspec
file via ./gradlew podspec
. It uses the name of the gradle project, which is also the default value. Any ideas?Artyom Degtyarev [JB]
11/30/2020, 8:15 AMAzur Haljeta
12/02/2020, 8:13 AMArtyom Degtyarev [JB]
12/04/2020, 1:40 PMshared
, located in /shared/build/xcode-frameworks/, execute packForXcode
script. I would guess this is the reason you see the wrong name - iosApp.xcodeproj is still looking for it and remembering it.
I’ve written an instruction on making standard project usable with cocoapods some time ago, maybe you could look it through for some advice. It can be found here.Azur Haljeta
12/04/2020, 2:23 PMframeworkName
specified in cocoapods{}
is ignored when building the .podspec
file via ./gradlew podspec
. It uses the name of the gradle project, which is also the default value.
If I have frameworkName = MyOwnPod
in the cocoapods{}
block, I also want to reference that same pod in the Podfile
like this: pod 'MyOwnPod', :path => '../shared'
. But I'm not able to do this since shared.podspec
has spec.name
equal to 'shared'
.podspec
filecocoapods{}
are parsed well in the .podspec
file. For example, spec.summary
is set to '`A nice pod'` which is exactly what's specified in cocoapods { summary }
. It's the same for other properties - but not for frameworkName
Artyom Degtyarev [JB]
12/04/2020, 3:16 PMAzur Haljeta
12/04/2020, 3:18 PM