Skip to content

Releases: ACINQ/phoenix

Phoenix Android v2.0.12

06 Nov 10:08
43e65cf
Compare
Choose a tag to compare

ℹ️ Migration for existing legacy wallets (v1.x)

Users upgrading from the legacy app (1.x) to 2.x will need to migrate to be able to use 2.x features. See the 2.0.0 release notes for details about the migration process. You can see what version you are currently using in Settings > About.

Changes from 2.0.11

  • Gracefully handle Android keystore failures at startup, and fall back to manual seed input to unlock the wallet.
    See 945b640 for details.
  • Fixed camera staying online after leaving the scan view. Thanks @kotasjan for the help!
    See issue #442 for details.
  • Several fixes and improvements. Thanks @MasterixCZ for the Czech localisation fixes.

Full changelog:

Verifying signatures

You will need gpg and our release signing key 7A73FE77DE2C4027. Note that you can get it:

To import our signing key:

$ gpg --import drouinf.asc

To verify the release file checksums and signatures:

$ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped
$ sha256sum -c SHA256SUMS.stripped

Phoenix Android v2.0.11

17 Oct 15:39
93b8289
Compare
Choose a tag to compare

Migration for existing legacy wallets (v1.x)

Users upgrading from the legacy app (1.x) to 2.x will need to migrate to be able to use 2.x features. See the 2.0.0 release notes for details about the migration process. You can see what version you are currently using in Settings > About.

Changes from 2.0.10

  • Display the grace-period for pending deposits in the swap-in screen. See #444 for details
  • Fix invalid intents from apps trying to open Phoenix to send a payment.
  • Fix an issue with the reserve that could trigger force-close, see ACINQ/lightning-kmp@6e4bc39

Full changelog:

Verifying signatures

You will need gpg and our release signing key 7A73FE77DE2C4027. Note that you can get it:

To import our signing key:

$ gpg --import drouinf.asc

To verify the release file checksums and signatures:

$ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped
$ sha256sum -c SHA256SUMS.stripped

Phoenix Android v2.0.10

10 Oct 11:42
838724a
Compare
Choose a tag to compare

Migration for existing legacy wallets (v1.x)

Users upgrading from the legacy app (1.x) to 2.x will need to migrate to be able to use 2.x features. See the 2.0.0 release notes for details about the migration process. You can see what version you are currently using in Settings > About.

Changes from 2.0.9

  • Updated the wording of the migration message in the legacy application. Added a date where some legacy services (swap-in and pay-to-open) will be disabled (November 1st).
  • 2 bug fixes in lightning-kmp.

Full changelog:

Verifying signatures

You will need gpg and our release signing key 7A73FE77DE2C4027. Note that you can get it:

To import our signing key:

$ gpg --import drouinf.asc

To verify the release file checksums and signatures:

$ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped
$ sha256sum -c SHA256SUMS.stripped

Phoenix Android v2.0.9

29 Sep 08:54
18c2d2a
Compare
Choose a tag to compare

Migration for existing legacy wallets (v1.x)

Users upgrading from the legacy app (1.x) to 2.x will need to migrate to be able to use 2.x features. See the 2.0.0 release notes for details about the migration process. You can see what version you are currently using in Settings > About.

Changes from 2.0.8

  • Added notice in home screen when incoming Lightning payments are rejected, to make them more visible.
  • Added the last swap-in failed attempt in the swap-in screen.
  • Several bug fixes in lightning-kmp.

Full changelog:

Verifying signatures

You will need gpg and our release signing key 7A73FE77DE2C4027. Note that you can get it:

To import our signing key:

$ gpg --import drouinf.asc

To verify the release file checksums and signatures:

$ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped
$ sha256sum -c SHA256SUMS.stripped

Phoenix Android v2.0.8

20 Sep 17:35
b545af3
Compare
Choose a tag to compare

Migration for existing legacy wallets (v1.x)

Users upgrading from the legacy app (1.x) to 2.x will need to migrate to be able to use 2.x features. See the 2.0.0 release notes for details about the migration process. You can see what version you are currently using in Settings > About.

Changes from 2.0.7

This is a bug fix release.

  • Fixed an issue where payment would be prevented when channels were in closing
  • Fixed an issue where swaps would not be attempted due to a race condition between the swap-in wallet and the peer connection.

Diff:

Verifying signatures

You will need gpg and our release signing key 7A73FE77DE2C4027. Note that you can get it:

To import our signing key:

$ gpg --import drouinf.asc

To verify the release file checksums and signatures:

$ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped
$ sha256sum -c SHA256SUMS.stripped

Phoenix Android 2.0.7

19 Sep 08:45
1e35745
Compare
Choose a tag to compare

Migration for existing legacy wallets (v1.x)

Users upgrading from the legacy app (1.x) to 2.x will need to migrate to be able to use 2.x features. See the 2.0.0 release notes for details about the migration process. You can see what version you are currently using in Settings > About.

Changes from 2.0.6

Electrum Client rework

The Electrum connection logic has been improved. There should be less issues with Electrum connection, especially when connection fails and needs to be reestablished. See ACINQ/lightning-kmp#512 for details

Increased size of logs export

The log file could be sometimes truncated by the SL4J rolling system which could result in less logs than available.

Added support for per-app localisation

Phoenix can now use a different language than the rest of the device. This feature is only available on Android 13+.

Improved Czech and French translation

Thanks @MasterixCZ for working on this.

Several bug fixes and UI improvements

Verifying signatures

You will need gpg and our release signing key 7A73FE77DE2C4027. Note that you can get it:

To import our signing key:

$ gpg --import drouinf.asc

To verify the release file checksums and signatures:

$ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped
$ sha256sum -c SHA256SUMS.stripped

Phoenix Android 2.0.6

13 Sep 13:28
354652d
Compare
Choose a tag to compare

Migration for existing legacy wallets (v1.x)

For users upgrading from the legacy Phoenix Android app (1.x) to 2.x, a migration is needed. See the 2.0.0 release notes for details about the migration process.

Changes from 2.0.5

Fixed several issues related to LNURL

  • withdrawals will now offer the user to withdraw the maximum amount available, instead of the minimum;
  • LUD-17 urls (starting with lnurlp, lnurlw, keyauth) are now properly parsed.

The Czech translation has been improved

Thanks @MasterixCZ and @margre8 for working on this.

Verifying signatures

You will need gpg and our release signing key 7A73FE77DE2C4027. Note that you can get it:

To import our signing key:

$ gpg --import drouinf.asc

To verify the release file checksums and signatures:

$ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped
$ sha256sum -c SHA256SUMS.stripped

Phoenix Android v2.0.5

01 Sep 19:04
e6bb471
Compare
Choose a tag to compare

Migration for existing legacy wallets (v1.x)

For users upgrading from the legacy Phoenix Android app (1.x) to 2.x, a migration is needed. See the 2.0.0 release notes for details about the migration process.

Changes from 2.0.4

Added localisation for 🇩🇪 German, 🇪🇸 Spanish, 🇵🇹 Portuguese and 🇨🇿 Czech localisation.

Thanks @myxmaster for the help with German translation!

Spanish, Portuguese, and Czech localisation are partial, and may not be accurate. However, it's still better than just displaying English.

Handle callback action for sucessful LNURL payments

Also, LNURL payments made prior to this version should display the successAction result correctly. See #404.

Add warning regarding legacy swap addresses

For users who migrate from v1.4.x, warnings have been added about reusing legacy swap-in addresses. These addresses should not be used anymore after migration. The new wallet will only support the new address displayed in the receive screen.

If an old legacy address has benn used after the migration is done, contact support: phoenix@acinq.co

Verifying signatures

You will need gpg and our release signing key 7A73FE77DE2C4027. Note that you can get it:

To import our signing key:

$ gpg --import drouinf.asc

To verify the release file checksums and signatures:

$ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped
$ sha256sum -c SHA256SUMS.stripped

Phoenix Android v2.0.4

30 Aug 09:29
d3c0aea
Compare
Choose a tag to compare

Migration for existing legacy wallets (v1.x)

For users upgrading from the legacy Android app (1.x) to Android 2.x, a migration is needed. See the 2.0.0 release notes for details about the migration process.

Changes from 2.0.2

This release fixes several issues and brings a few improvements in the app.

Swaps are now attempted at each block

Previous versions required the app to be restarted in order to attempt pending swap-ins. This is not the case anymore, the app will attempt swaps at each new block. System notifications for failed swaps have been reduced to prevent spam.

Added link to scanner in receive screen

Receiving funds over LNURL required users to click on Send in order to open the scanner, which is counterintuitive. This has been fixed by adding back the "Use LNURL link" button in the Receive screen, like in the legacy app.

Other

  • Reconnecting to the Peer and the Electrum servers should be snappier
  • Fixed an issue where connection to the Peer would not be made (#400)

Verifying signatures

You will need gpg and our release signing key 7A73FE77DE2C4027. Note that you can get it:

To import our signing key:

$ gpg --import drouinf.asc

To verify the release file checksums and signatures:

$ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped
$ sha256sum -c SHA256SUMS.stripped

Android v2.0.2

24 Aug 13:09
21e65e4
Compare
Choose a tag to compare

This release bumps the minimal Android version to android 8+ to prevent installing the app on old, incompatible devices.

Users with Android 7.1 or older can still use version 1.4.27, but we strongly recommend upgrading to a recent Android version that receives security patches.

Migration for existing wallets

For users upgrading from the legacy app (1.x) to the new app, a migration is needed. See the 2.0.0 release notes for details about the migration process.

Verifying signatures

You will need gpg and our release signing key 7A73FE77DE2C4027. Note that you can get it:

To import our signing key:

$ gpg --import drouinf.asc

To verify the release file checksums and signatures:

$ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped
$ sha256sum -c SHA256SUMS.stripped