[expo-update][android] Upgrade test packages and remove mockito (#15565)
[expo-updates][android] Use immutable fields in UpdatesConfiguration (#15558)
[expo-updates][android] Kotlinize expo-updates (#14818)
[expo-updates] store assets with filename = key.fileExtension (#13801)
[expo-updates] allow & handle nullable asset keys in application code (#12111)
[expo-updates] add unit tests for manifest classes (#11562)Added native unit tests for the following things: - legacy manifest required fields - new (EAS) manifest required fields - manifest cre
[expo-updates] add unit tests for manifest classes (#11562)Added native unit tests for the following things: - legacy manifest required fields - new (EAS) manifest required fields - manifest creation (that the correct class is used depending on the type of manifest) - added a bit more coverage to the existing tests around asset base urls Additionally, writing these tests exposed some discrepancies between/within platforms about handling possibly null manifest fields, so I fixed those.
show more ...
[expo-updates][expo] add warning/error in JS if neither runtime nor SDK version are defined (#11367)
[expo-updates] fix Android unit tests
[expo-updates] add scopeKey field to configuration and use when interacting with database (#9217)# Why Allow updates for multiple projects to be stored in the same database. # How We previ
[expo-updates] add scopeKey field to configuration and use when interacting with database (#9217)# Why Allow updates for multiple projects to be stored in the same database. # How We previously added the project_identifier field in the database for this purpose -- it is meant to be a unique ID for a project that can be used to filter stored updates by project. This commit adds a migration to turn that field into `scope_key`, adds a corresponding `scopeKey` field to the updates configuration object, and uses this `config.scopeKey` field both when inserting and selecting updates from the database. If no `scopeKey` is specified, it defaults to the manifest (update) URL origin. # Test Plan No behavior changes are expected, this just adds functionality that will be utilized when integrating the module into the App Store clients. Added some unit tests for the URL origin normalization logic.
[expo-updates] add android instrumentation test runner and database unit tests (#9238)
[expo-updates] add some basic unit tests (#8986)