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
From what I've read, Realm should be only 1-2MB. However, when uploading a build to App Store Connect with Realm included in an App Clip, it is over 30MB when using Swift Package Manager and prevents the build from being accepted.
This is the size when using XCFramework directly:
This is the error from App Store Connect:
This is the size when using Swift Package Manager:
As you can see, using the Swift package manager version increases the app clip size by nearly 25MB. Even without Swift Package Manager, the size is over 10MB.
How can I get Realm to be the 1-2MB small size?
Stacktrace & log output
No response
Can you reproduce the bug?
-- select --
Reproduction Steps
No response
Version
10.54.0
What Atlas Services are you using?
-- select --
Are you using encryption?
-- select --
Platform OS and version(s)
iOS App Clip
Build environment
No response
The text was updated successfully, but these errors were encountered:
Description
From what I've read, Realm should be only 1-2MB. However, when uploading a build to App Store Connect with Realm included in an App Clip, it is over 30MB when using Swift Package Manager and prevents the build from being accepted.
This is the size when using XCFramework directly:
This is the error from App Store Connect:
This is the size when using Swift Package Manager:
As you can see, using the Swift package manager version increases the app clip size by nearly 25MB. Even without Swift Package Manager, the size is over 10MB.
How can I get Realm to be the 1-2MB small size?
Stacktrace & log output
No response
Can you reproduce the bug?
-- select --
Reproduction Steps
No response
Version
10.54.0
What Atlas Services are you using?
-- select --
Are you using encryption?
-- select --
Platform OS and version(s)
iOS App Clip
Build environment
No response
The text was updated successfully, but these errors were encountered: