Skip to content

Release 0.5.16: gate plugin flags on the iOS device build path too#16

Merged
GenericJam merged 1 commit into
masterfrom
gate-ios-device-plugin-flags
Jun 2, 2026
Merged

Release 0.5.16: gate plugin flags on the iOS device build path too#16
GenericJam merged 1 commit into
masterfrom
gate-ios-device-plugin-flags

Conversation

@GenericJam
Copy link
Copy Markdown
Owner

0.5.15 gated Android + iOS-sim plugin flags but missed zig_build_binary_ios_device, which still emitted -Dplugin_swift_files/-Dplugin_frameworks (and generated the bootstrap, making plugin_swift_files always non-empty) unconditionally. So mix mob.deploy --native to a physical iPhone broke on an app scaffolded before the plugin system (invalid option: -Dplugin_swift_files). The device path now mirrors the sim path — bootstrap + flags only when plugins are activated.

Verified: mix mob.deploy --native to a physical iPhone (iPhone SE 3rd gen) → full OTP, Phoenix endpoint up, LiveView socket connected, embedded Livebook home mounted. 105 native_build tests pass.

🤖 Generated with Claude Code

0.5.15 gated Android + iOS-sim but missed zig_build_binary_ios_device, which
still emitted -Dplugin_swift_files/-Dplugin_frameworks (+ generated the
bootstrap) unconditionally — so `mix mob.deploy --native` to a physical iPhone
broke on pre-plugin app scaffolding. The device path now mirrors the sim path.

Verified: mob.deploy --native to a physical iPhone → full OTP, Phoenix up,
LiveView connected, embedded Livebook home rendered.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@GenericJam GenericJam merged commit 7873c59 into master Jun 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant