noise: after update to 3.30.0 sending messages not working #600

Closed
greycanary opened this Issue Feb 22, 2017 · 4 comments

Comments

Projects
None yet
2 participants
@greycanary

Hi,

didn't know where to file a bug report - hopefully this is the right place!

Since I updated Noise from 3.29.2 to 3.30.0 it doesn't send any encrypted signal messages anymore! Receiving Messages works fine though!

It says I should activate SMS-Support and/or register Signal again to send encrypted Signal Messages (instead of SMS).

Same thing at another device - both devices run CyanogenMod 13 / Android 6.

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Feb 22, 2017

Contributor

Did you accept the notice asking you to enable video / voice support? It will ask you to register again and not doing that after you click the notice might break it.

Contributor

thestinger commented Feb 22, 2017

Did you accept the notice asking you to enable video / voice support? It will ask you to register again and not doing that after you click the notice might break it.

@thestinger thestinger closed this Feb 22, 2017

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Feb 22, 2017

Contributor

It's essentially an unmodified Signal now so I disabled the issue tracker there and I don't plan on taking bug reports for it. I think I know what's wrong with the transition but it's a bit late to change that now.

Contributor

thestinger commented Feb 22, 2017

It's essentially an unmodified Signal now so I disabled the issue tracker there and I don't plan on taking bug reports for it. I think I know what's wrong with the transition but it's a bit late to change that now.

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Feb 22, 2017

Contributor

There a new Signal 3.30.2 anyway so it's now part of that.

Contributor

thestinger commented Feb 22, 2017

There a new Signal 3.30.2 anyway so it's now part of that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment