cafu2500

Debugged in 3.14.7 now, and found that a change in SqliteDdlReader seems to be the cause on Android, opened issue now as https://www.symmetricds.org/issues/view.php?id=5933 (table_xinfo not bringing results on Android (at least not on Android Studio's simulator))

Further checks: Android-3.12.23 suffers from https://www.symmetricds.org/issues/view.php?id=5289 Android-3.14.0 and -3.14.1 suffer from the below error (communication locks?), but at least seem to create tables and start working, but cannot finish syncing with the central server: 2023-07-22 21:52:07.092 6512-6633 o.j.s.r.DataGapRou com.ms.shoppinglist V Querying for gaps 1 through 1 of total 1 2023-07-22 21:52:07.095 6512-6633 o.j.s.r.Configurat com.ms.shoppinglist D Completing batch 3 2023-07-22...

Trying to find out since when this is going wrong, unfortunately Android-3.13.0 suffers from recursion (https://www.symmetricds.org/issues/view.php?id=5289 ), and Android-3.13.5 and Android-3.13.12 suffer from 2023-07-22 21:20:07.486 5733-6167 o.j.s.s.i.DataLoa com.ms.shoppinglist E Failed to process batch org.apache.commons.lang3.NotImplementedException at org.jumpmind.symmetric.android.AndroidSymmetricEngine.getMonitorService(AndroidSymmetricEngine.java:226) at org.jumpmind.symmetric.common.ConfigurationChangedHelper.contextCommitted(ConfigurationChangedHelper.java:145)...

I've been running a SymmetricDS server 3.12.13 with Android Apps on SymmetricDS-Android 3.12.9. I now tried to update both to 3.14.8. Server is running successful on 3.14.8, even interacts without issues with the old Android-3.12.9 clients (or a SymmetricDS-Android-3.12.9 client installed on a wiped device). When I try to create a new Android app with SymmetricDS-Android-3.14.8, I'm running into deep trouble: 1) If I'm installing the app-update on top of the old app, it has a failure to read the...

No, node.offline is not used. With "offline" I was just referring to Android devices temporarily not running the app (and the SymmetricDS service) for some time (might be 7-14 days). Sorry if that was misleading. Long running transactions - don't think so. As mentioned other devices sync the same changes correct, so routing definitely processed it for those node_ids. I now changed purge.retention.minutes to 40320 ( = 28 days) on centre and hope to see something useful in sym_data, sym_data_event...

I'm suffering from a problem where from time to time I lose data and despite checking sym_data, sym_data_event, sym_outgoing_batch, ... and the incoming/outgoing files was not yet able to track down the reason. It seems the routing fails to create some outgoing batches for targets that are offline for some time, but I can't find a reason. I know it's difficult to advise without a concrete reproducible scenario, but I hope for a hint where to look or where to enlarge periods (e.g. purge times?) to...

Thanks for the confirmation. I was aware of the sym_extension table, but I prefer IDE support and therefore "real" classes. Android-specific SymDS documentation seems a bit scarce ;-), but now I think I achieved what I wanted to ... although it took a lot of debugging and code study ;-)

I'm still wondering how to register an extension in SymmetricDS in Android "the official way". I managed on a Windows machine (symmetric-extensions.xml), and I managed to do it the following way in Android: engine = AndroidSymmetricEngine.findEngineByName(ENGINE_NAME); engine.getExtensionService().addExtensionPoint(new MyExtensionImplementation()); But I guess this is not the best / the only way?