We have tested it successfully with 4 nodes last week at the Fusion Festival in Germany - one of those where you have to battle constant cellular network outages - and were surprised to randomly see fellow meshtastic users extending the mesh network. It was one of those "open source technology is amazing" moments :D.
It sounds to me like it's not because of your skills and experience. You have been working in your field for a long time. Very few developers are "rock stars". We all build on the shoulders of giants - sticking code together is a pragmatic approach - especially if you work for a startup. But it sounds to me like you're comparing yourself too much to your ideal. My tip: Compare yourself less with "rockstars", learn the skills you are really interested in and reduce your working hours to a bearable level.
Without knowing the App, but the location permission could be required for Bluetooth 4.X LE to work. That still doesn't justify why a dryer needs your phonebook.
one of the best tools for reverse engineering mobile apps.
I'm just having problems when certificate pinning is enabled. Does anyone have an idea (or even a solution) how to deal with that?
Even without certificate pinning, starting with Android 7, you must decompile the app to allow user provided certificates. Or use an xposed module if you have a rooted device.
Also, if the app uses Google signin, you have to be rooted, because play services uses the package manager to check the app signer before giving the app a token.
Same here, mitmproxy was always the goto tool, but many apps now use certificate pinning, which stops it cold.
I was recently wishing for a "Jailbroken Mobile Testing Tool", similar to Sauce Labs or BrowserStack but with jailbroken mobiles -- i.e. a cloud-based service allowing you to remotely control a mobile phone through a web interface. Would that be interesting to have?
This service would allow you to load an app from the App Store / Google Play, and then interact with it while logging all network connections (in tcpdump/wireshark/HAR/etc. format). The controlled mobiles would be jailbroken and have tools like SSL kill switch (as mentioned by @bitexploder in another comment) installed by default.
(Going further: the same tool would allow you to download the phone's storage as a zip archive for further analysis)
It's been a while, but when I have been reversing android apps with certificate pinning in the past, I had the most luck with decompiling the apk with apktool, removing the certificate pinning in the samli bytecode, then recompiling and signing the apk again.
For iOS, I know there are jailbreak cydia tweaks that try to disable certificate pinning, but I have no experience with this.
We deal with this routinely. Solutions tend to vary.
On iOS just use SSL kill switch (if you are jailbroken). If you are not jailbroken you don't have a lot of options. On Android there are some well documented approaches. Usually decompiling the app and adding to the local app's cert store will work and then rearchive and sign it.
Function hooking key network calls can work as well. It is pretty much required that if you want to do serious tinkering or assessment you need a jailbroken or rooted device. This can be a significant effort investment, but once done is generally reliable.
I can highly recommend a visit there. Not only you can see an original Z4 and a replica of the Z3, but also lot's of more science and history related exhibitions. Don't miss the Enigma!
