Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Error when exporting framework: unexpected binary name … Static libraries should be prefixed with lib

Open
#1 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
ios, swift

Research direction

Start by reproducing the failure with skip export in the skip-gmaps project and inspect the generated .build/artifacts/ios-maps-sdk/GoogleMaps/GoogleMaps.xcframework path. Compare failed and successful export runs, then verify that iOS export completes reliably without the unexpected binary-name error; no source file or test is named in the issue.

Written by the indexing model from the issue text.

Description

When trying to skip export this framework (or any app that uses it), it fails at the iOS stage:

error: unexpected binary name at .build/artifacts/ios-maps-sdk/GoogleMaps/GoogleMaps.xcframework/ios-arm64/GoogleMaps.a. Static libraries should be prefixed with lib

The underlying issue is open at https://issuetracker.google.com/issues/466122128.

But if try running skip export multiple times, it will eventually work:

zap skiptools/skip-gmaps [main] % skip export          

[✓] Check Swift Package (0.62s)
[✓] Getting SDK Path (0.01s)
[✗] Build project skip-gmaps (21.95s)
[✗] error: unexpected binary name at /opt/src/github/skiptools/skip-gmaps/.build/artifacts/ios-maps-sdk/GoogleMaps/GoogleMaps.xcframework/ios-arm64/GoogleMaps.a. Static libraries should be prefixed with lib
error: unexpected binary name at /opt/src/github/skiptools/skip-gmaps/.build/artifacts/ios-maps-sdk/GoogleMaps/GoogleMaps.xcframework/ios-arm64/GoogleMaps.a. Static libraries should be prefixed with lib
[✗] Skip 1.8.2 export failed with 2 errors
See https://skip.dev/docs/faq and https://forums.skip.dev for help
See output log for error details: /tmp/skip-export-2026-03-31T14:16:02Z.txt
Error: 3 errors

zap skiptools/skip-gmaps [main] % skip export 

[✓] Check Swift Package (0.25s)
[✓] Getting SDK Path (0.01s)
[✗] Build project skip-gmaps (1.14s)
[✗] error: unexpected binary name at /opt/src/github/skiptools/skip-gmaps/.build/artifacts/ios-maps-sdk/GoogleMaps/GoogleMaps.xcframework/ios-arm64/GoogleMaps.a. Static libraries should be prefixed with lib
error: unexpected binary name at /opt/src/github/skiptools/skip-gmaps/.build/artifacts/ios-maps-sdk/GoogleMaps/GoogleMaps.xcframework/ios-arm64/GoogleMaps.a. Static libraries should be prefixed with lib
[✗] Skip 1.8.2 export failed with 2 errors
See https://skip.dev/docs/faq and https://forums.skip.dev for help
See output log for error details: /tmp/skip-export-2026-03-31T14:16:31Z.txt
Error: 3 errors

zap skiptools/skip-gmaps [main] % skip export

[✓] Check Swift Package (0.26s)
[✓] Getting SDK Path (0.01s)
[✓] Build project skip-gmaps (0.7s)
[✓] Assemble frameworks for SkipGMaps (25.67s)
[✓] Export SkipFoundation-debug.aar: 1.2 MB
[✓] Export SkipGMaps-debug.aar: 88 KB
[✓] Export SkipLib-debug.aar: 1.7 MB
[✓] Export SkipModel-debug.aar: 85 KB
[✓] Export SkipUI-debug.aar: 6.5 MB
[✓] Export SkipUnit-debug.aar: 13 KB
[✓] Export SkipFoundation-release.aar: 1.1 MB
[✓] Export SkipGMaps-release.aar: 81 KB
[✓] Export SkipLib-release.aar: 1.6 MB
[✓] Export SkipModel-release.aar: 80 KB
[✓] Export SkipUI-release.aar: 5.8 MB
[✓] Export SkipUnit-release.aar: 12 KB
[✓] Export project for SkipGMaps
[✓] Archive project source SkipGMaps-project.zip 4.8 MB
[✓] Skip export skip-gmaps to ./.build/skip-export (28.29s)
[✓] Skip 1.8.2 export succeeded in 28.3s

Also note that you can manually build and archive an app that uses this library, you just cannot export the iOS half of the app. In addition, skip export --android will work.

Dominant language
Swift
Stars
2
Forks
0
PR merge metrics
No merged PRs in 30d

Getting set up

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.

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.