swagger-api / swagger-api/swagger-codegen

Swagger-codegen for objc doesn't work - produces invalid cocoa pod

Open
#8,182 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Mustache
Stars
17.8k
Forks
6k
PR merge metrics
No merged PRs in 30d

Description

Description

Swagger-codegen for objc doesn't work - produces invalid cocoa pod when checked via lint. See below.

Swagger-codegen version

2.3.1

Swagger declaration file content or url

https://api.cloudmersive.com/specs/allapis.json

Command line used for generation

Standard, see above

Steps to reproduce
  1. Run swagger-codegen for objectivec on this spec URL:

https://api.cloudmersive.com/specs/allapis.json

  1. Then run "pod lib lint" on a mac to check validity

Expected: No errors

Observed: Errors - see below

Error:

Cloudmersive.APIClient.Cocoa andrewbragdon$ pod lib lint

-> cloudmersive (1.0.0)
- ERROR | [iOS] unknown: Encountered an unknown error (/usr/bin/xcrun simctl list -j devices

dyld: Symbol not found: _SimDeviceBootKeyDisabledJobs
Referenced from: /Applications/Xcode.app/Contents/Developer/usr/bin/simctl
Expected in: /Library/Developer/PrivateFrameworks/CoreSimulator.framework/Versions/A/CoreSimulator
in /Applications/Xcode.app/Contents/Developer/usr/bin/simctl
) during validation.

[!] cloudmersive did not pass validation, due to 1 error.
You can use the --no-clean option to inspect any issue.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by generating the Objective-C client from https://api.cloudmersive.com/specs/allapis.json with swagger-codegen 2.3.1, then run “pod lib lint” on macOS and compare the result with the reported xcrun/simctl error. Confirm whether the failure is in the generated CocoaPod or the local Xcode/CoreSimulator environment; done means the cause is identified and the reproduction is resolved or documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
objective-c
Domain
mobile-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.