Skip to content

Note that custom event classes need DispatchableFromNative - #18

Open
simonhamp wants to merge 1 commit into
mainfrom
security/dispatchable-from-native
Open

simonhamp wants to merge 1 commit into
mainfrom
security/dispatchable-from-native

Conversation

@simonhamp

Copy link
Copy Markdown
Member

nativephp/mobile 4.6.1 and 3.3.11 fixed GHSA-83jv-8h7x-287p. The /_native/api/events endpoint now refuses to build any class that doesn't implement Native\Mobile\Events\Contracts\DispatchableFromNative.

This plugin lets an app pass its own class to event(), and native sends that class back through the same endpoint. An app class without the marker is now refused and never fires, with no error. Core's default event already has the marker, so only custom classes are affected.

This adds a note and a short example where event() is documented. No code changes.

🤖 Generated with Claude Code

nativephp/mobile 4.6.1 and 3.3.11 refuse event classes sent back from
native unless they implement
Native\Mobile\Events\Contracts\DispatchableFromNative
(GHSA-83jv-8h7x-287p). A class passed to event() goes the same way, so
say so where event() is documented.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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