Add podspecs in correct Cocoapods layout

[kuhnroyal]

Follow up to my comments in #91

I tried this with a private repo and it works well.
Alternatively you could create some https://github.com/m0nac0/flutter-maplibre-specs repo for this.

Build will fail until this is available in the default branch of either repository.

[kuhnroyal]

@m0nac0 My tests with this Spec repo layout were successful. Everything in this PR works, just need a place to store the specs in the correct layout. Makes everything much easier.

You can test it locally with this repo: https://github.com/source-kitchen/flutter-maplibre-podspecs
You can clone this and use it as starting point for a new repo, don't fork as I plan to remove it ASAP.

[m0nac0]

@kuhnroyal I've created https://github.com/m0nac0/flutter-maplibre-podspecs. Would you like to adapt this PR?

[m0nac0]

Not sure why the CI is failing

[kuhnroyal]

Yea me neither, I updated the example Podfile.lock and XCode files, hope that helps. The Podfile.lock should be committed to Git.

[m0nac0]

Can you try re-adding the pod update step in the CI to check if that's the issue?

And when you tested this yourself, did you test with the example app or your own project?

[kuhnroyal]

It runs locally, so I am not sure, will try.

[kuhnroyal]

Not sure why, don't need that locally for the example or my own app.

[kuhnroyal]

The pod update was not needed, the problem was related to some Podfile miss configuration for the simulator target.

[kuhnroyal]

This should be fine now and can be squashed probably.

[m0nac0]

I added one small request, otherwise this looks good.

[kuhnroyal]

I added one small request, otherwise this looks good.

Can't see it :)

[m0nac0]

Sorry, I left the comment as "pending" review and missed your reply. It should be visible now?

[kuhnroyal]

Done

[m0nac0]

One more thing: do we need example/pubspec.yaml to be committed to the repo or is this just an artifact of the change to .gitignore?

[kuhnroyal]

One more thing: do we need example/pubspec.yaml to be committed to the repo or is this just an artifact of the change to .gitignore?

I would always commit the pubspec.lock for apps because this prevents accidental breakage, especially in CI.
For libraries this is not recommended but I believe for apps this is the correct way.

[m0nac0]

@kuhnroyal Thanks again for your patience!