basically we do not normally have login/logout in the app, but only with a fresh install. This has never been a problem as in our experience once they login the first time, then they are logged in forever (like years), and the data is always pushed correctly.
After sunday however data was not pushed for some users, the ones using this Pro web service noticed (or coaches working with athletes via the web service, as the regular user of the app cannot see the issue since locally it is all working normally).
Hence we added a login button in the app, to see if by logging in they could then get their data synched, and this seems to do the trick.
It seems like if with the migration some users were logged out but then when opening the app the system does not detect it the way it normally would (so the user can proceed using the app without having to login again, which normally would be the case when we detect that the user is online but logged out - rare situation based on what I mentioned above)
I am sorry but I am not really able to provide more useful information as I cannot replicate this on our devices where every phone stayed logged in even after the migration, so this is a best guess based on what has been reported by users.
hi Olha, I still experience this issue (it is a problem as I need to be able to export the data, otherwise I am stuck here without access). Here is the error I see:
1 07:21:54 EXPORT Export started
2 07:21:54 EXPORT Exporting table: BackendlessFile
3 07:21:54 EXPORT Exporting table: PurchaseOrderTest
4 07:21:54 EXPORT Exporting table: DailySummaryNoCoreData
5 07:24:49 EXPORT Exporting table DailySummaryNoCoreData failed Exception:com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Application was streaming results when the connection failed. Consider raising value of ‘net_write_timeout’ on the server.
6
7 sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
8 sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
9 sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
10 java.lang.reflect.Constructor.newInstance(Constructor.java:423)
11 com.mysql.jdbc.Util.handleNewInstance(Util.java:404)
12 com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:983)
13 com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:3457)
14 com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:3357)
15 com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3797)
16 com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:871)
17 com.mysql.jdbc.MysqlIO.nextRow(MysqlIO.java:1963)
18 com.mysql.jdbc.RowDataDynamic.nextRecord(RowDataDynamic.java:375)
19 com.mysql.jdbc.RowDataDynamic.next(RowDataDynamic.java:355)
20 com.mysql.jdbc.ResultSetImpl.next(ResultSetImpl.java:6344)
21 org.apache.commons.dbcp2.DelegatingResultSet.next(DelegatingResultSet.java:191)
22 com.backendless.tasks.impex.DataTableExporter.execute(DataTableExporter.java:96)
23 com.backendless.tasks.impex.ExportTask.export(ExportTask.java:154)
24 com.backendless.tasks.impex.ExportTask.execute(ExportTask.java:108)
25 com.backendless.taskman.Task.run(Task.java:123)
26 java.lang.Thread.run(Thread.java:748)
27 Caused by: java.io.EOFException: Can not read response from server. Expected to read 1,081 bytes, read 211 bytes before connection was unexpectedly lost.
28
29 com.mysql.jdbc.MysqlIO.readFully(MysqlIO.java:2949)
30 com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:3417)
31 com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:3357)
32 com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3797)
33 com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:871)
34 com.mysql.jdbc.MysqlIO.nextRow(MysqlIO.java:1963)
35 com.mysql.jdbc.RowDataDynamic.nextRecord(RowDataDynamic.java:375)
36 com.mysql.jdbc.RowDataDynamic.next(RowDataDynamic.java:355)
37 com.mysql.jdbc.ResultSetImpl.next(ResultSetImpl.java:6344)
38 org.apache.commons.dbcp2.DelegatingResultSet.next(DelegatingResultSet.java:191)
39 com.backendless.tasks.impex.DataTableExporter.execute(DataTableExporter.java:96)
40 com.backendless.tasks.impex.ExportTask.export(ExportTask.java:154)
41 com.backendless.tasks.impex.ExportTask.execute(ExportTask.java:108)
42 com.backendless.taskman.Task.run(Task.java:123)
43 java.lang.Thread.run(Thread.java:748)
44 07:24:49 EXPORT Exporting table: CoachNoCoreData
45 07:24:50 EXPORT Exporting table: CoachRequestNoCoreData
46 07:24:50 EXPORT Exporting table: LapOnline
47 07:25:15 EXPORT Exporting table: ReferralCode
48 07:25:15 EXPORT Exporting table: PPGOnline
49 07:25:16 EXPORT Exporting table: CustomPlan
50 07:25:16 EXPORT Exporting table: DailySummary
51 07:25:19 EXPORT Exporting table: Loggers
52 07:25:19 EXPORT Exporting table: Users
53 07:25:21 EXPORT Exporting table: RROnline
54 07:25:22 EXPORT Exporting table: PlanningDailySummary
55 07:25:23 EXPORT Exporting table: PurchaseOrder
56 07:25:23 EXPORT Exporting table: PlanningOverview
57 07:25:23 EXPORT Exporting table: SubscriptionNoCoreData
58 07:25:23 EXPORT Exporting table: UserUpdateNoCoreData
59 07:25:24 EXPORT Generating export.zip
60 07:27:43 EXPORT Uploading export.zip to File Service
61 07:27:45 EXPORT Export finished
Thank you for your help
please somebody look into this, we need to export the data. Thank you
@mark-piller
Hi @Alessandra_Saviotti,
Thank you for your patience. We worked quite hard to get this problem resolved. It should be working now. Please check. Also, it would be quite beneficial for the continued smooth operation to keep the file storage of your app as clean as possible (removing older unused large files).
Regards,
Mark
1 Like
thank you Mark, this is really appreciated. I hope you and your team are doing well in these challenging times.