App not reproducible
See original GitHub issueComparing APKs latest version 2.1.14 from github https://github.com/btcontract/wallet/releases/download/2.1.14/SBW-2.1.14.apk to APK from fdroid: https://f-droid.org/repo/com.btcontract.wallet_75.apk
Result in diff in several files:
diff --recursive --brief ./SBW-2.1.14/ ./com.btcontract.wallet_75/
Only in ./SBW-2.1.14/assets: graph.snapshot-mainnet.zlib
Files ./SBW-2.1.14/classes3.dex and ./com.btcontract.wallet_75/classes3.dex differ
Files ./SBW-2.1.14/classes.dex and ./com.btcontract.wallet_75/classes.dex differ
Files ./SBW-2.1.14/lib/arm64-v8a/libsecp256k1.so and ./com.btcontract.wallet_75/lib/arm64-v8a/libsecp256k1.so differ
Files ./SBW-2.1.14/lib/arm64-v8a/libwallycore.so and ./com.btcontract.wallet_75/lib/arm64-v8a/libwallycore.so differ
Files ./SBW-2.1.14/lib/armeabi-v7a/libsecp256k1.so and ./com.btcontract.wallet_75/lib/armeabi-v7a/libsecp256k1.so differ
Files ./SBW-2.1.14/lib/armeabi-v7a/libwallycore.so and ./com.btcontract.wallet_75/lib/armeabi-v7a/libwallycore.so differ
Files ./SBW-2.1.14/lib/x86/libsecp256k1.so and ./com.btcontract.wallet_75/lib/x86/libsecp256k1.so differ
Files ./SBW-2.1.14/lib/x86/libwallycore.so and ./com.btcontract.wallet_75/lib/x86/libwallycore.so differ
Files ./SBW-2.1.14/lib/x86_64/libsecp256k1.so and ./com.btcontract.wallet_75/lib/x86_64/libsecp256k1.so differ
Files ./SBW-2.1.14/lib/x86_64/libwallycore.so and ./com.btcontract.wallet_75/lib/x86_64/libwallycore.so differ
- why file
graph.snapshot-mainnet.zlib
not exists in f-droid version? is it a bug that should be opened in their gitlab? - diffoscope https://diffoscope.org/ should be run on both files to look into the diffs in the files.
- in what environment the github APK was build, as the diffs are probably caused by it.
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
How to Reproduce a Non-Reproducible Defect and Make ...
Always recheck your steps to reproduce on a new system, clearing all cookies and cache memory. Make sure the sentences are short and...
Read more >How to Deal with Non Reproducible Bug - Onecore
Let's say a bug appears during the installation of the software under particular operating system with specific memory.Same bug doesn't appear under another ......
Read more >When the bug is 'non-reproducible'... - LinkedIn
A bug could be because you didn't let that “pull to refresh” complete. And as Devs are often running the app in simulators...
Read more >Any good strategies for dealing with 'not reproducible' bugs?
If all else fails, try looking at the section of code that is causing problems, and possibly refactor or use a workaround. If...
Read more >5 Simple Ways to Reproduce Not Reproducible Bug
5 Simple Ways to Reproduce Not Reproducible Bug ; 1. SnagIt Video Recorder ; 2. psr.exe – problem steps recorder in Windows 7...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’ve identified a few advanced Scala features which seemingly do not play well with reproducibility (chunks of code get moved around non-deterministically while compiling), currently doing some refactoring to get rid of those and hopefully in next release this will be resolved.
Tested version 2.2.15.1 sha256sum for https://github.com/btcontract/wallet/releases/download/2.2.15.1/SBW-2.2.15.1.apk is:
26851863c62f4114009c1d5cab95610d9d93035714153466d89be28d4b57af4b
Running
./gradlew assembleRelease
in above container:app is reproducible as brief diff is: