The entries still appear in the app and haven't been transfered back to org mode. Captures afterwards have been successfully synced.
I am using ssh/scp sync mode.
Try clearing the database in "settings" and synch again. If the problem persists it might be fixed with the next release. If it's not, please re-open this issue.
I'm not sure I understand what your problem is. What do you mean with "stuck"? Captured nodes with "Capture child" should generate edit nodes for org-mode to synch and modify the local database. As soon as that particular file is changed by org-mode, mobileorg will overwrite the file, losing any changes only in the database.
The next release changes how the database is accessed, so be prepared to lose anything not synched to org-mode on the next upgrade. Do you need help recovering your files, or could you manually (copy/paste) backup your data?
The nodes are displayed in the app but haven't generated edit nodes.
The data is mostly in outline format, and mixed in with existing entries, so extracting manually would be tedious and error prone. I would like some way to recover this data.
I have also similar problem with the newest compiled release. After capturing a new node below an existing org mode file and synchronizing, the orgmode.org file stays unchanged at my UbuntuOne account. However editing a single node adds the F(edit:heading)... etc. to the orgmode.org file.
Editing the newly created but "hanging" node also creates the edit entry in the orgmode.org file, but gives error when pulling from org-mode.
Finally the "hanging" nodes remain in mobileorg without any error until the database is cleared.
I use the newest compiled version of mobileorg and UbuntuOne for sync, but have similar experiences also with the SD-card sync.
Would a recovery function that writes an entire file of the database as plain text org-mode to sdcard work?
The current release includes a "Recover" function from the actionbar menu that can dump an entire file to logcat. Hope this helps.