Emanoil Kotsev <[email protected]> writes: > Hi, > It is the file UPGRADING.txt in openobex not the README > Upgrading to version 1.7Upgrading to version 1.6
1.7 is ancient (released 2016). I remember reading about "When using an event loop that triggers on incoming data, you must call OBEX_HandleInput() after each call to OBEX_Request() to actually send the request" (https://gitlab.com/openobex/mainline/-/blob/master/UPGRADING.txt). If I remember correctly, my conclusion was that SyncEvolution does that, but I am not sure anymore. > regards > On Thursday, July 30, 2020, 1:08:31 AM GMT+2, Emanoil Kotsev > <[email protected]> wrote: > > Hi,strange I do not see this on the ML. > I don't know how to debug this. The problem is that openobex changed - if you > look in the README it says what needs to be done to upgrade from 1.5 to 1.7.I > did not have time and ability to go deeper into openobex. > The problem is that after SAN is sent it (syncevolution) hangs waiting for > PUT or whatever and does not move forward. > > I tried few weeks ago building bueto-syncml for the (now) Sailfish OS > with openobex 1.7 and I had syncevolution 1.5.3 with openobex 1.5 on > the PC, but it hangs on the phone the same way it hangs on the PC if > it is build against openobex 1.7. I couldn't find out, how I can get > log from the plugin there as it is started in a thread an nothing > logs. Can you ensure that you have working setup and then just update the SyncEvolution side to openobex 1.7? Does that then start to fail? It's not clear to me from the description above whether that is something that you have tested. -- Best Regards Patrick Ohly _______________________________________________ SyncEvolution mailing list -- [email protected] To unsubscribe send an email to [email protected] %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
