Comments (8)
Fantastic - thank you very much for this great info.
I've flagged the empty zip file to engineering. We have been able to reproduce this and it looks like something that occurs sometimes on Windows machines when using Windows File Explorer to unzip the file. If you unzip with a third-party app such as 7-Zip, the zip should contain the expected contents. We're working on improvements to better support this with Windows File Explorer. Sorry for the inconvenience, and thank you for reporting it so we can investigate.
Regarding the problems with the Kotlin template app, we'll use this info to do some exploration. We hope to get back to you soon. Thank you for the helpful info, and for your patience while we investigate!
from realm-template-apps.
Hey @cudawarped - it looks like the Sync-related issues may be due to an issue when creating a template app. That issue may have been resolved with an internal release yesterday. If you create a new template app, hopefully everything will work. Or if you still have problems, creating a new App Services App without a template, and then configuring things manually, would be another possible workaround.
Let me know if this resolves your issue!
from realm-template-apps.
Let me know if this resolves your issue!
Hi @dacharyc, I created a new template app and now its all working perfectly, thank you for all you help.
from realm-template-apps.
Hey there - sorry you're having trouble with the template app. Are you on a Windows machine, by chance? The zip issue has been reported before, but we've had trouble replicating it - I'm wondering if our zips aren't working for Windows.
The Reading failed: End of input
message can occur for a few different reasons. Sometimes it is a transient error that resolves itself. If you leave the app running for a moment, does it resolve, or does it continue outputting this message? You can also change the log level to stop seeing this message: https://www.mongodb.com/docs/realm/sdk/kotlin/logging/
Regarding the black screen, a few more details could help us try to replicate your issue:
- What emulator or device are you using to run the app?
- What version of the Kotlin SDK are you running?
- Do the App Services logs contain any additional information or errors? You can get information about viewing those logs here in our View Application Logs documentation.
from realm-template-apps.
Hi, thank you for your quick response.
Hey there - sorry you're having trouble with the template app. Are you on a Windows machine, by chance? The zip issue has been reported before, but we've had trouble replicating it - I'm wondering if our zips aren't working for Windows.
Yes I'm trying to download the zip on windows.
The Reading failed: End of input message can occur for a few different reasons. Sometimes it is a transient error that resolves itself. If you leave the app running for a moment, does it resolve, or does it continue outputting this message? You can also change the log level to stop seeing this message: https://www.mongodb.com/docs/realm/sdk/kotlin/logging/
After changing the debug level to LogLevel.DEBUG
I get the following output from logcat
-
Launching the app through the debugger for the first time I am presented with the login screen. After I login I get a black screen with the following logcat output
Login logcat
2024-02-15 12:02:21.099 10658-10658 LoginEvent com.mongodb.app I User logged in successfully. 2024-02-15 12:02:25.585 10658-10759 REALM com.mongodb.app W [Core] Reading failed: End of input 2024-02-15 12:02:29.885 10658-10759 REALM com.mongodb.app W [Core] Reading failed: End of input 2024-02-15 12:02:34.165 10658-10759 REALM com.mongodb.app W [Core] Reading failed: End of input 2024-02-15 12:02:38.460 10658-10759 REALM com.mongodb.app W [Core] Reading failed: End of input 2024-02-15 12:02:42.747 10658-10759 REALM com.mongodb.app W [Core] Reading failed: End of input 2024-02-15 12:02:46.701 10658-10759 REALM com.mongodb.app W [Core] Reading failed: End of input 2024-02-15 12:02:50.981 10658-10759 REALM com.mongodb.app W [Core] Reading failed: End of input 2024-02-15 12:02:55.354 10658-10759 REALM com.mongodb.app W [Core] Reading failed: End of input 2024-02-15 12:02:59.667 10658-10759 REALM com.mongodb.app W [Core] Reading failed: End of input 2024-02-15 12:03:03.970 10658-10759 REALM com.mongodb.app W [Core] Reading failed: End of input 2024-02-15 12:03:07.178 10658-10759 REALM com.mongodb.app W [Core] Reading failed: End of input 2024-02-15 12:03:11.477 10658-10759 REALM com.mongodb.app W [Core] Reading failed: Premature end of input 2024-02-15 12:03:15.775 10658-10759 REALM com.mongodb.app W [Core] Reading failed: End of input 2024-02-15 12:03:20.064 10658-10759 REALM com.mongodb.app W [Core] Reading failed: End of input 2024-02-15 12:03:24.413 10658-10759 REALM com.mongodb.app W [Core] Reading failed: End of input 2024-02-15 12:03:28.727 10658-10759 REALM com.mongodb.app W [Core] Reading failed: End of input 2024-02-15 12:03:33.037 10658-10759 REALM com.mongodb.app W [Core] Reading failed: End of input 2024-02-15 12:03:37.334 10658-10759 REALM com.mongodb.app W [Core] Reading failed: End of input 2024-02-15 12:03:41.625 10658-10759 REALM com.mongodb.app W [Core] Reading failed: End of input 2024-02-15 12:03:45.924 10658-10759 REALM com.mongodb.app W [Core] Reading failed: End of input 2024-02-15 12:03:50.222 10658-10759 REALM com.mongodb.app W [Core] Reading failed: End of input 2024-02-15 12:03:54.543 10658-10759 REALM com.mongodb.app W [Core] Reading failed: Premature end of input
-
If I restart the app through the debugger it gets stuck on a white android splash screen with the following logs
First restart
2024-02-15 12:04:32.694 10923-10958 REALM com.mongodb.app W [Core] Reading failed: End of input 2024-02-15 12:04:36.996 10923-10958 REALM com.mongodb.app W [Core] Reading failed: End of input 2024-02-15 12:04:41.304 10923-10958 REALM com.mongodb.app W [Core] Reading failed: End of input 2024-02-15 12:04:45.593 10923-10958 REALM com.mongodb.app W [Core] Reading failed: End of input 2024-02-15 12:04:49.897 10923-10958 REALM com.mongodb.app W [Core] Reading failed: End of input 2024-02-15 12:04:54.189 10923-10958 REALM com.mongodb.app W [Core] Reading failed: End of input 2024-02-15 12:04:58.489 10923-10958 REALM com.mongodb.app W [Core] Reading failed: End of input 2024-02-15 12:05:02.817 10923-10958 REALM com.mongodb.app W [Core] Reading failed: End of input 2024-02-15 12:05:07.138 10923-10958 REALM com.mongodb.app W [Core] Reading failed: End of input
-
Restarting as second time takes me to the list view which repeats the following output
List view logcat
2024-02-15 12:05:42.932 11075-11108 REALM com.mongodb.app D [Core] Connection[1]: Closing the websocket with status='SystemError: End of input', was_clean='false' 2024-02-15 12:05:42.932 11075-11108 REALM com.mongodb.app D [Core] Connection[1]: Connection closed due to error 2024-02-15 12:05:42.933 11075-11108 REALM com.mongodb.app D [Core] WebSocket::Websocket() 2024-02-15 12:05:42.934 11075-11108 REALM com.mongodb.app D [Core] Resolving 'ws.eu-central-1.aws.realm.mongodb.com:443' 2024-02-15 12:05:42.939 11075-11108 REALM com.mongodb.app D [Core] Connecting to endpoint '35.157.33.91:443' (1/3) 2024-02-15 12:05:42.986 11075-11108 REALM com.mongodb.app D [Core] Connected to endpoint '35.157.33.91:443' (from '10.0.2.16:34620') 2024-02-15 12:05:43.035 11075-11108 REALM com.mongodb.app D [Core] Verifying server SSL certificate using root certificates, host name = ws.eu-central-1.aws.realm.mongodb.com, server port = 443, certificate = -----BEGIN CERTIFICATE----- MIIFYDCCBEigAwIBAgIQQAF3ITfU6UK47naqPGQKtzANBgkqhkiG9w0BAQsFADA/ MSQwIgYDVQQKExtEaWdpdGFsIFNpZ25hdHVyZSBUcnVzdCBDby4xFzAVBgNVBAMT DkRTVCBSb290IENBIFgzMB4XDTIxMDEyMDE5MTQwM1oXDTI0MDkzMDE4MTQwM1ow TzELMAkGA1UEBhMCVVMxKTAnBgNVBAoTIEludGVybmV0IFNlY3VyaXR5IFJlc2Vh cmNoIEdyb3VwMRUwEwYDVQQDEwxJU1JHIFJvb3QgWDEwggIiMA0GCSqGSIb3DQEB AQUAA4ICDwAwggIKAoICAQCt6CRz9BQ385ueK1coHIe+3LffOJCMbjzmV6B493XC ov71am72AE8o295ohmxEk7axY/0UEmu/H9LqMZshftEzPLpI9d1537O4/xLxIZpL wYqGcWlKZmZsj348cL+tKSIG8+TA5oCu4kuPt5l+lAOf00eXfJlII1PoOK5PCm+D LtFJV4yAdLbaL9A4jXsDcCEbdfIwPPqPrt3aY6vrFk/CjhFLfs8L6P+1dy70sntK 4EwSJQxwjQMpoOFTJOwT2e4ZvxCzSow/iaNhUd6shweU9GNx7C7ib1uYgeGJXDR5 bHbvO5BieebbpJovJsXQEOEO3tkQjhb7t/eo98flAgeYjzYIlefiN5YNNnWe+w5y sR2bvAP5SQXYgd0FtCrWQemsAXaVCg/Y39W9Eh81LygXbNKYwagJZHduRze6zqxZ Xmidf3LWicUGQSk+WT7dJvUkyRGnWqNMQB9GoZm1pzpRboY7nn1ypxIFeFntPlF4 FQsDj43QLwWyPntKHEtzBRL8xurgUBN8Q5N0s8p0544fAQjQMNRbcTa0B7rBMDBc SLeCO5imfWCKoqMpgsy6vYMEG6KDA0Gh1gXxG8K28Kh8hjtGqEgqiNx2mna/H2ql PRmP6zjzZN7IKw0KKP/32+IVQtQi0Cdd4Xn+GOdwiK1O5tmLOsbdJ1Fu/7xk9TND TwIDAQABo4IBRjCCAUIwDwYDVR0TAQH/BAUwAwEB/zAOBgNVHQ8BAf8EBAMCAQYw SwYIKwYBBQUHAQEEPzA9MDsGCCsGAQUFBzAChi9odHRwOi8vYXBwcy5pZGVudHJ1 c3QuY29tL3Jvb3RzL2RzdHJvb3RjYXgzLnA3YzAfBgNVHSMEGDAWgBTEp7Gkeyxx +tvhS5B1/8QVYIWJEDBUBgNVHSAETTBLMAgGBmeBDAECATA/BgsrBgEEAYLfEwEB ATAwMC4GCCsGAQUFBwIBFiJodHRwOi8vY3BzLnJvb3QteDEubGV0c2VuY3J5cHQu b3JnMDwGA1UdHwQ1MDMwMaAvoC2GK2h0dHA6Ly9jcmwuaWRlbnRydXN0LmNvbS9E U1RST09UQ0FYM0NSTC5jcmwwHQYDVR0OBBYEFHm0WeZ7tuXkAXOACIjIGlj26Ztu MA0GCSqGSIb3DQEBCwUAA4IBAQAKcwBslm7/DlLQrt2M51oGrS+o44+/yQoDFVDC 5WxCu2+b9LRPwkSICHXM6webFGJueN7sJ7o5XPWioW5WlHAQU7G75K/QosMrAdSW 9MUgNTP52GE24HGNtLi1qoJFlcDyqSMo59ahy2cI2qBDLKobkx/J3vWraV0T9VuG WCLKTVXkcGdtwlfFRjlBz4pYg1htmf5X6DYO8A4jqv2Il9DjXA6USbW1FzXSLr9O he8Y4IWS6wY7bCkjCWDcRQJMEhg76fsO3txE+FiYruq9RUWhiF1myv4Q6W+CyBFC Dfvp7OOGAN6dEOM4+qR9sdjoSYKEBpsr6GtPAQw4dy753ec5 -----END CERTIFICATE----- 2024-02-15 12:05:43.035 11075-11108 REALM com.mongodb.app D [Core] Verifying server SSL certificate using 155 root certificates 2024-02-15 12:05:43.043 11075-11108 REALM com.mongodb.app D [Core] Server SSL certificate verified using root certificate(37): -----BEGIN CERTIFICATE----- MIIDSjCCAjKgAwIBAgIQRK+wgNajJ7qJMDmGLvhAazANBgkqhkiG9w0BAQUFADA/MSQwIgYD VQQKExtEaWdpdGFsIFNpZ25hdHVyZSBUcnVzdCBDby4xFzAVBgNVBAMTDkRTVCBSb290IENB IFgzMB4XDTAwMDkzMDIxMTIxOVoXDTIxMDkzMDE0MDExNVowPzEkMCIGA1UEChMbRGlnaXRh bCBTaWduYXR1cmUgVHJ1c3QgQ28uMRcwFQYDVQQDEw5EU1QgUm9vdCBDQSBYMzCCASIwDQYJ KoZIhvcNAQEBBQADggEPADCCAQoCggEBAN+v6ZdQCINXtMxiZfaQguzH0yxrMMpb7NnDfcdA wRgUi+DoM3ZJKuM/IUmTrE4Orz5Iy2Xu/NMhD2XSKtkyj4zl93ewEnu1lcCJo6m67XMuegwG MoOifooUMM0RoOEqOLl5CjH9UL2AZd+3UWODyOKIYepLYYHsUmu5ouJLGiifSKOeDNoJjj4X Lh7dIN9bxiqKqy69cK3FCxolkHRyxXtqqzTWMIn/5WgTe1QLyNau7Fqckh49ZLOMxt+/yUFw 7BZy1SbsOFU5Q9D8/RhcQPGX69Wam40dutolucbY38EVAjqr2m7xPi71XAicPNaDaeQQmxkq tilX4+U9m5/wAl0CAwEAAaNCMEAwDwYDVR0TAQH/BAUwAwEB/zAOBgNVHQ8BAf8EBAMCAQYw HQYDVR0OBBYEFMSnsaR7LHH62+FLkHX/xBVghYkQMA0GCSqGSIb3DQEBBQUAA4IBAQCjGiyb FwBcqR7uKGY3Or+Dxz9LwwmglSBd49lZRNI+DT69ikugdB/OEIKcdBodfpga3csTS7MgROSR 6cz8faXbauX+5v3gTt23ADq1cEmv8uXrAvHRAosZy5Q6XkjEGB5YGV8eAlrwDPGxrancWYaL bumR9YbK+rlmM6pZW87ipxZzR8srzJmwN0jP41ZL9c8PDHIyh8bwRLtTcm1D9SZImlJnt1ir /md2cXjbDaJWFBM5JDGFoqgCWjBH4d1QB7wCCZAA62RjYJsWvIjJEubSfZGL+T0yjWW06Xyx V3bqxbYoOb8VZRzI9neWagqNdwvYkQsEjgfbKbYK7p2CNTUQ -----END CERTIFICATE----- 2024-02-15 12:05:43.044 11075-11108 REALM com.mongodb.app D [Core] WebSocket::initiate_client_handshake() 2024-02-15 12:05:43.106 11075-11108 REALM com.mongodb.app D [Core] WebSocket::handle_http_response_received() 2024-02-15 12:05:43.107 11075-11108 REALM com.mongodb.app D [Core] Connection[1]: Negotiated protocol version: 8 2024-02-15 12:05:43.107 11075-11108 REALM com.mongodb.app D [Core] Connection[1]: Connected to app services with request id: "65cde1f778ecd276c0e7678b" 2024-02-15 12:05:43.107 11075-11108 REALM com.mongodb.app D [Core] Connection[1]: Will emit a ping in 44194 milliseconds 2024-02-15 12:05:43.107 11075-11108 REALM com.mongodb.app D [Core] Connection[1]: Session[1]: Sending: BIND(session_ident=1, need_client_file_ident=true is_subserver=false json_data="") 2024-02-15 12:05:43.218 11075-11108 REALM com.mongodb.app D [Core] Connection[1]: Closing the websocket with status='OK: ', was_clean='true' 2024-02-15 12:05:47.222 11075-11108 REALM com.mongodb.app W [Core] Reading failed: End of input
-
Adding an entry to the list updates the android UI but I can't see any thing under Data Services -> Browse Collections
Adding list entry logcat
2024-02-15 12:06:41.140 11075-11160 REALM com.mongodb.app D [Core] DB: 13280 Thread 138663685070064: Open file: /data/user/0/com.mongodb.app/files/mongodb-realm/application-1-ouyre/server-utility/metadata/sync_metadata.realm 2024-02-15 12:06:41.141 11075-11160 REALM com.mongodb.app D [Core] DB: 13280 Thread 138663685070064: DB closed 2024-02-15 12:06:41.143 11075-11107 REALM com.mongodb.app D [Core] DB: 5064 Thread 138663712566512: Initiate commit version: 9 2024-02-15 12:06:41.149 11075-11107 REALM com.mongodb.app D [Core] DB: 5064 Thread 138663712566512: Commit of size 2560 done in 6580 us 2024-02-15 12:06:41.151 11075-11108 REALM com.mongodb.app D [Core] Connection[1]: Session[1]: Progress handler called, downloaded = 0, downloadable(total) = 0, uploaded = 0, uploadable = 372, reliable_download_progress = false, snapshot version = 9 2024-02-15 12:06:41.151 11075-11109 REALM com.mongodb.app D [Core] DB: 5064 Thread 138663710444784: Query find all: 'TRUEPREDICATE and TRUEPREDICATE', limit = -1 2024-02-15 12:06:41.152 11075-11108 REALM com.mongodb.app D [Core] Connection[1]: Session[1]: Progress handler called, downloaded = 0, downloadable(total) = 0, uploaded = 0, uploadable = 372, reliable_download_progress = false, snapshot version = 9 2024-02-15 12:06:41.151 11075-11109 REALM com.mongodb.app D [Core] DB: 5064 Thread 138663710444784: Query found: 2, Duration: 25 us 2024-02-15 12:06:41.151 11075-11109 REALM com.mongodb.app D [Core] DB: 5064 Thread 138663710444784: Query find all: 'TRUEPREDICATE and TRUEPREDICATE', limit = -1 2024-02-15 12:06:41.151 11075-11109 REALM com.mongodb.app D [Core] DB: 5064 Thread 138663710444784: Query found: 2, Duration: 1 us 2024-02-15 12:06:41.155 11075-11075 CoroutineScope com.mongodb.app E Task 'MutableState(value=newer item)@200548823' added successfully. 2024-02-15 12:06:41.156 11075-11075 REALM com.mongodb.app D [Core] DB: 5064 Thread 138677243081976: Query find all: 'TRUEPREDICATE and TRUEPREDICATE', limit = -1 2024-02-15 12:06:41.156 11075-11075 REALM com.mongodb.app D [Core] DB: 5064 Thread 138677243081976: Query found: 2, Duration: 6 us 2024-02-15 12:06:41.167 11075-11075 REALM com.mongodb.app D [Core] DB: 13280 Thread 138677243081976: Open file: /data/user/0/com.mongodb.app/files/mongodb-realm/application-1-ouyre/server-utility/metadata/sync_metadata.realm 2024-02-15 12:06:41.169 11075-11075 REALM com.mongodb.app D [Core] DB: 13280 Thread 138677243081976: DB closed 2024-02-15 12:06:41.183 11075-11075 WindowOnBackDispatcher com.mongodb.app W sendCancelIfRunning: isInProgress=falsecallback=ImeCallback=ImeOnBackInvokedCallback@198129332 Callback=android.window.IOnBackInvokedCallback$Stub$Proxy@e11aec0 2024-02-15 12:06:41.184 11075-11075 WindowOnBackDispatcher com.mongodb.app W sendCancelIfRunning: isInProgress=falsecallback=android.view.ViewRootImpl$$ExternalSyntheticLambda17@e229095 2024-02-15 12:06:41.243 11075-11102 OpenGLRenderer com.mongodb.app D endAllActiveAnimators on 0x7e1dd68abfd0 (UnprojectedRipple) with handle 0x7e1ee6d169e0 2024-02-15 12:06:41.351 11075-11075 REALM com.mongodb.app D [Core] DB: 13280 Thread 138677243081976: Open file: /data/user/0/com.mongodb.app/files/mongodb-realm/application-1-ouyre/server-utility/metadata/sync_metadata.realm 2024-02-15 12:06:41.352 11075-11075 REALM com.mongodb.app D [Core] DB: 13280 Thread 138677243081976: DB closed 2024-02-15 12:06:41.386 11075-11102 EGL_emulation com.mongodb.app D app_time_stats: avg=214.26ms min=0.85ms max=6463.92ms count=31 2024-02-15 12:06:41.392 11075-11075 RemoteInpu...ectionImpl com.mongodb.app W getSurroundingText on inactive InputConnection 2024-02-15 12:06:41.429 11075-11075 ImeBackDispatcher com.mongodb.app E Ime callback not found. Ignoring unregisterReceivedCallback. callbackId: 198129332 2024-02-15 12:06:42.580 11075-11108 REALM com.mongodb.app W [Core] Reading failed: End of input
Regarding the black screen, a few more details could help us try to replicate your issue:
- What emulator or device are you using to run the app?
I was using a Pixel 7 Hardware device but I have now switched to an emulated Pixel 7 Pro with API 34.
- What version of the Kotlin SDK are you running?
1.8.0. The templated app has the following kotlin related entries
id("io.realm.kotlin") version "1.8.0"
implementation("org.jetbrains.kotlinx:kotlinx-coroutines-core:1.6.4")
implementation("io.realm.kotlin:library-sync:1.8.0")
classpath("org.jetbrains.kotlin:kotlin-gradle-plugin:1.7.20")
- Do the App Services logs contain any additional information or errors? You can get information about viewing those logs here in our View Application Logs documentation.
The App Services log look successful, just repeating the below
JSON logs
{
"logs": [{
"_id": "65cde3e11747838ce1aae99f",
"co_id": "65cde3df1747838ce1aace94",
"type": "SYNC_CONNECTION_END",
"user_id": "65cddc34c0d9920386fe948a",
"domain_id": "65cdd9a670d3ac10ab7f79d2",
"app_id": "65cdd9a670d3ac10ab7f79d1",
"group_id": "65cdd7bb3f25c9093f9c4d73",
"request_url": "/api/client/v2.0/app/application-1-ouyre/realm-sync",
"request_method": "GET",
"remote_ip_address": "109.242.76.186",
"started": "2024-02-15T10:13:53.716Z",
"completed": "2024-02-15T10:13:53.716Z",
"function_call_location": "DE-FF",
"function_call_provider_region": "aws-eu-central-1",
"status": 101,
"messages": ["Connection was active for: 2s"],
"platform": "Android",
"platform_version": "14",
"sdk_name": "Kotlin",
"sdk_version": "1.8.0",
"framework_name": "Android",
"framework_version": "34"
}, {
"_id": "65cde3df1747838ce1aacfa8",
"co_id": "65cde3df1747838ce1aace94",
"type": "SYNC_SESSION_START",
"user_id": "65cddc34c0d9920386fe948a",
"domain_id": "65cdd9a670d3ac10ab7f79d2",
"app_id": "65cdd9a670d3ac10ab7f79d1",
"group_id": "65cdd7bb3f25c9093f9c4d73",
"request_url": "/api/client/v2.0/app/application-1-ouyre/realm-sync",
"request_method": "GET",
"remote_ip_address": "109.242.76.186",
"started": "2024-02-15T10:13:51.647Z",
"completed": "2024-02-15T10:13:51.714Z",
"function_call_location": "DE-FF",
"function_call_provider_region": "aws-eu-central-1",
"messages": ["Sync client has disconnected from the server. The client will automatically reconnect."],
"platform": "Android",
"platform_version": "14",
"sdk_name": "Kotlin",
"sdk_version": "1.8.0",
"framework_name": "Android",
"framework_version": "34"
}, {
"_id": "65cde3df1747838ce1aacecc",
"co_id": "65cde3df1747838ce1aace94",
"type": "SYNC_CONNECTION_START",
"user_id": "65cddc34c0d9920386fe948a",
"domain_id": "65cdd9a670d3ac10ab7f79d2",
"app_id": "65cdd9a670d3ac10ab7f79d1",
"group_id": "65cdd7bb3f25c9093f9c4d73",
"request_url": "/api/client/v2.0/app/application-1-ouyre/realm-sync",
"request_method": "GET",
"remote_ip_address": "109.242.76.186",
"started": "2024-02-15T10:13:51.617Z",
"completed": "2024-02-15T10:13:51.617Z",
"function_call_location": "DE-FF",
"function_call_provider_region": "aws-eu-central-1",
"platform": "Android",
"platform_version": "14",
"sdk_name": "Kotlin",
"sdk_version": "1.8.0",
"framework_name": "Android",
"framework_version": "34"
}, {
"_id": "65cde3dd1747838ce1aab246",
"co_id": "65cde3db1747838ce1aa9a96",
"type": "SYNC_CONNECTION_END",
"user_id": "65cddc34c0d9920386fe948a",
"domain_id": "65cdd9a670d3ac10ab7f79d2",
"app_id": "65cdd9a670d3ac10ab7f79d1",
"group_id": "65cdd7bb3f25c9093f9c4d73",
"request_url": "/api/client/v2.0/app/application-1-ouyre/realm-sync",
"request_method": "GET",
"remote_ip_address": "109.242.76.186",
"started": "2024-02-15T10:13:49.433Z",
"completed": "2024-02-15T10:13:49.433Z",
"function_call_location": "DE-FF",
"function_call_provider_region": "aws-eu-central-1",
"status": 101,
"messages": ["Connection was active for: 2s"],
"platform": "Android",
"platform_version": "14",
"sdk_name": "Kotlin",
"sdk_version": "1.8.0",
"framework_name": "Android",
"framework_version": "34"
}]
}
from realm-template-apps.
One more follow-up - the template app version is behind the current SDK version. You might try bumping the Kotlin SDK version in your client code from 1.8.0 to 1.13.0, which is the current version. There have been a handful of fixes between then and now that might have resolved the issues you're seeing. We'll put up a PR to bump this dependency in the template app once we've had a chance to test it internally, but wanted to flag it here in case you want to try that to see if it resolves your issue.
from realm-template-apps.
If you unzip with a third-party app such as 7-Zip, the zip should contain the expected contents.
Now I feel stupid, I didn't even think to try another app, 7-Zip worked perfectly thank you.
One more follow-up - the template app version is behind the current SDK version. You might try bumping the Kotlin SDK version in your client code from 1.8.0 to 1.13.0, which is the current version.
The result is the same with 1.13.0. Is it possible that I have missed something when configuring App and/or Data Services? Are you able to sync successfuly by following the tutorial?
from realm-template-apps.
Sorry for the delay in getting back to you - I wanted to take the time to test this before answering. Yes, I am able to sync successfully when I run the app.
We have pushed an update to this template app to update to Kotlin SDK version 1.13.0. It seems you already performed that update yourself, so I presume that won't solve your issue.
I don't have an Android hardware device or Windows machine to test this myself, so I'll forward this report to the SDK engineers. Hopefully they'll have some additional troubleshooting suggestions.
from realm-template-apps.
Related Issues (16)
- The react-native template pulled from realm platform does not initiate correctly with xcode 69.5 HOT 2
- the layout ressource is not in the project HOT 1
- Crash on Mac Catalyst (SwiftUI)
- Where is the getUserItems defined? HOT 1
- Call To Function is not passing the arguments HOT 2
- SwiftUI template app unable to maintain connection with flexible sync HOT 2
- .net maui template app HOT 1
- `flutter run macos` fails to build on M1 HOT 1
- React Native todo app get stuck on npm and crashes when built on Mac HOT 11
- Flutter - atlasUrl is missing in config HOT 2
- Realm Prop load error HOT 7
- EMpty template app HOT 3
- SwiftUI project doesn't work in offline mode when upgrading to latest package version. HOT 5
- Android todo app doesn't sync and crashes when pressing subscription button HOT 3
- Errors with repo: missing path-browserify,hermes realm init error whenever @realm/react Providers are used HOT 5
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from realm-template-apps.