## Amber 4.0.0
- Refactor everything to use the new quartz update
- Fix reconnection issues
- Kill switch feature
Download it with [zap.store](https://zapstore.dev/download), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v4.0.0)
If you like my work consider making a [donation](https://greenart7c3.com)
## Verifying the release
In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:
``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```
Once you have his PGP key you can verify the release (assuming `manifest-v4.0.0.txt` and `manifest-v4.0.0.txt.sig` are in the current directory) with:
``` bash
gpg --verify manifest-v4.0.0.txt.sig manifest-v4.0.0.txt
```
You should see the following if the verification was successful:
``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```
That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:
``` bash
cat manifest-v4.0.0.txt
```
One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.
Login to reply
Replies (11)
It doesn't seem it hit fdroid yet.
there is an issue with the new version
it is already bad when the app can't be updated in obtainium
we tested zaps on this noteβ¦ we made one attempts toβ‘zap this note, at chill-bill@wmdpi.com, over a period of about 60 seconds. in each case, we found that your lightning address service or server did not respond correctly. if you wanted to fix this... you could try getting a free rizful lightning address -- https://rizful.com ... if u get it set up, pls reply here so we can do this β‘zap test again.
The best tool around. Let's update!
nostr:nevent1qqswdh0pm38c9czwrfz2d0tcnvdtjhqkkcwl3uyhdca90ahxwrvyzuspz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsyg8wuwg7as64rmfrh9ssyl0zx4wq7tvf4y467jvdnd6gvdmc6zuhcgpsgqqqqqqsuy4ss6
Noob question: how do I get this working with Amethyst on Android?
I installed zapstore just a few minutes ago, and then Amber 4.0.0, and I have put my nsec into Amber
Do I need to remove my nsec from Amethyst, and configure it to use Amber instead?
... to answer my own question: I eventually found Amethyst's logout option and then logged in with Amber


Your link to zapstore links to old url which is now used by some shitcoin project. The correct url is https://zapstore.dev/
Thanks
Amber Crashes to Initial Screen After Adding 10+ Keys (v4.0.0)
Description: When adding approximately 10 or more keys to Amber, the app fails to load the key list upon reopening and instead reverts to the initial setup screen. This issue persists even after reinstalling the app.
Steps to Reproduce:
1. Install Amber v4.0.0 on an Android device.
2. Add keys one by one until reaching 10 or more (e.g., 10β15 keys).
3. Close the app completely.
Reopen the app.
4. Observe that the app does not display the key list and instead shows the initial setup screen.
Environment:
Amber Version: v4.0.0
Installation Source: Obtainium (https://github.com/greenart7c3/Amber/releases/download/v4.0.0/amber-offline-arm64-v8a-v4.0.0.apk)
Android Version: Android 12
Device Model: Samsung Galaxy Note10+
You can use obtainium
Could not reproduce this, tried using a note 9.