You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The ~MOB sigil now warns about iOS-only and Android-only tags
(MOB-194). The whitelist check tested the union of priv/tags/ios.txt and priv/tags/android.txt, so its iOS-only /
Android-only branches could never fire: a tag one platform does not render
compiled silently. A tag on exactly one manifest now warns at compile time,
naming the platform that has it; a tag on neither still warns that it is not
in the whitelist. Tags from config :mob, :extra_tags and plugin manifests
stay silent.
Anchored is on the Android tag whitelist (MOB-365). The Android bridge
has rendered :anchored since mob_new 0.5.0 (MOB-189), but priv/tags/android.txt did not list it, so with the fix above ~MOB(<Anchored>) would have warned that it is iOS-only. It was the only
tag on one manifest and not the other, so the two manifests now list the
same tags and no existing ~MOB usage gains a warning in this release.
iOS: a notification that arrives while the app is open now stays in
Notification Center (MOB-353). The notification delegate presented
foreground notifications with a banner and sound only; without UNNotificationPresentationOptionList, iOS 14+ does not add them to
Notification Center, so once the banner timed out the notification was
gone and could not be tapped later. The change is in ios/mob_nif.m: an
app gets it by updating mob and rebuilding natively
(mix mob.deploy --native).