Noise crashes initiating call, Signal does not #605

Closed
vvug opened this Issue Mar 10, 2017 · 4 comments

Comments

Projects
None yet
2 participants
@vvug

vvug commented Mar 10, 2017

Cable is affected by this bug, affecting self-compiled versions of Signal:

WhisperSystems/Signal-Android#6355

The bug does not affect the official Signal builds.

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Mar 10, 2017

Contributor

We don't make any changes to Signal, so it doesn't make sense to report issues here. Noise is simply a rebranded build and is explicitly not going to carry any patches to the code anymore. That means no upstream issues are going to be fixed even if it would only require changing one line of code. This is also the issue tracker for CopperheadOS and Noise isn't part of CopperheadOS.

Contributor

thestinger commented Mar 10, 2017

We don't make any changes to Signal, so it doesn't make sense to report issues here. Noise is simply a rebranded build and is explicitly not going to carry any patches to the code anymore. That means no upstream issues are going to be fixed even if it would only require changing one line of code. This is also the issue tracker for CopperheadOS and Noise isn't part of CopperheadOS.

@thestinger thestinger closed this Mar 10, 2017

@vvug

This comment has been minimized.

Show comment Hide comment
@vvug

vvug Mar 10, 2017

@thestinger I know, but as Noise always crashes when starting a call, while Signal never crashes, and the source is the same, then the problem is clearly with your build process.

If you don't want to see these bugs reported here just open the issue tracker for Noise. Where do you expect people reporting them?

vvug commented Mar 10, 2017

@thestinger I know, but as Noise always crashes when starting a call, while Signal never crashes, and the source is the same, then the problem is clearly with your build process.

If you don't want to see these bugs reported here just open the issue tracker for Noise. Where do you expect people reporting them?

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Mar 10, 2017

Contributor

It's not my code, so I don't really want to receive bug reports for it. I disabled the issue tracker once having a fork with changes was no longer necessary.

then the problem is clearly with your build process.

It's not my build process. It's the standard build process they provide. You said yourself that you run into the problem with your own builds of Signal.

If Noise is going to create maintenance / support work, I can just stop providing it and have people download the Signal web site builds that update themselves and require unknown sources enabled. I am only providing a more convenient option under the condition that it's not taking much time.

Contributor

thestinger commented Mar 10, 2017

It's not my code, so I don't really want to receive bug reports for it. I disabled the issue tracker once having a fork with changes was no longer necessary.

then the problem is clearly with your build process.

It's not my build process. It's the standard build process they provide. You said yourself that you run into the problem with your own builds of Signal.

If Noise is going to create maintenance / support work, I can just stop providing it and have people download the Signal web site builds that update themselves and require unknown sources enabled. I am only providing a more convenient option under the condition that it's not taking much time.

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Mar 10, 2017

Contributor

I would rather just redistribute their Play builds via our F-Droid repository if it was permitted...

Contributor

thestinger commented Mar 10, 2017

I would rather just redistribute their Play builds via our F-Droid repository if it was permitted...

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