Crash on first startup about axolotl HOT 7 CLOSED

I tried to skip registration by copying the contents of /home/phablet/.local/share/textsecure.jani/.storage to /home/phablet/.local/share/textsecure.nanuc/.storage. However, by doing so, I wasn’t able to send any messages.
Probably this is due to the missing file /home/phablet/.config/textsecure.nanuc/config.yml. Could you maybe share an updated template for that file? In textsecure.jani it currently containts

tel: "[my cell number]"
server: https://textsecure-service.whispersystems.org:443
rootCA: ""
proxy: ""
verificationType: sms
storageDir: /home/phablet/.local/share/textsecure.jani/.storage
unencryptedStorage: true
storagePassword: ""
loglevel: debug
userAgent: TextSecure 0.3.12 for Ubuntu Phone
alwaysTrustPeerID: true

Thanks at lot for forking this app and trying to maintain it better!

from axolotl.

Oeh, nice. I’ve figured by reading the source that the following will do:

tel: "[my cell number]"
server: https://textsecure-service.whispersystems.org:443
rootCA: ""
proxy: ""
verificationType: sms
storageDir: /home/phablet/.local/share/textsecure.nanuc/.storage
unencryptedStorage: true
storagePassword: ""
loglevel: debug
userAgent: TextSecure 0.3.18 for Ubuntu Phone
alwaysTrustPeerID: true

It worked indeed! Thanks again for squatting some of the bugs in the jani version! Great work!

Although I’ve now successfully worked around this bug, you might want to fix it for other new users of your app as well :)

from axolotl.

The Problem is
panic: cannot find descendant with objectName == "signInPage"
In the corresponding line the gofunction searches for an qml objectname, which exists and isn't found. The only thing i changed in the main.qml is updating the qtquick and the ubuntu.components version.

import QtQuick 2.4
import Ubuntu.Components 1.3

So for me this is a bug in the go<->qml bridge

from axolotl.

The sync devices qr-code scan page needs

import QtQuick 2.4
import Ubuntu.Components 1.3

so I can disable that and it's working again

from axolotl.

I cannot comment on whether that would indeed resolve the issue, or if it hasn’t any side effect, but great if you found the bug that quickly!

from axolotl.

Same here. crash

from axolotl.

This should be now resolved!!!

from axolotl.