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
default_bundle_version is now visible and editable. The column was fillable but missing from Version::toArray() and from the version forms, so it never appeared in a response and could not be set
from the dashboard. The version endpoints now return it, and both the create and edit forms expose a
"Default bundle version" field. Version.ts declares the field as well — the frontend decoder only
keeps the fields a model lists, so a response key alone would still have been dropped.
Fixed
default_bundle_version could never be written through the API.VersionController::store and ::update derive the writable attributes from the model's validation rules
(array_diff(array_keys($rules), ['file'])), and the field was in neither the Create nor the Update
set. That is what made /ota-client/v1/app/info answer 400 "Invalid bundle version" for a device
reporting the bundle name embedded in its APK — the case default_bundle_version exists to accept.