Hi! I maintain a personal fork of OpenBubbles with UI-only customizations.
The public source build uses the OpenAbsinthe stub, so Mac-hardware IDS registration cannot complete in my custom APK. I confirmed that Apple Account auth itself succeeds, but registration reaches the validation-data path and the public stub hits its unimplemented code.
I am not looking to bypass Apple's security or redistribute proprietary components. I also do not want to extract the closed implementation from a release binary or rely on reverse-engineered offsets.
Is there an officially supported or authorized way for a personal custom build to use the same production Absinthe/validation implementation that the distributed OpenBubbles app uses?
If not, is the intended position that fully functional custom builds from the public source tree are currently unsupported?
Thanks — I mainly want to keep my UI changes while using the normal OpenBubbles registration flow safely.
Hi! I maintain a personal fork of OpenBubbles with UI-only customizations.
The public source build uses the OpenAbsinthe stub, so Mac-hardware IDS registration cannot complete in my custom APK. I confirmed that Apple Account auth itself succeeds, but registration reaches the validation-data path and the public stub hits its unimplemented code.
I am not looking to bypass Apple's security or redistribute proprietary components. I also do not want to extract the closed implementation from a release binary or rely on reverse-engineered offsets.
Is there an officially supported or authorized way for a personal custom build to use the same production Absinthe/validation implementation that the distributed OpenBubbles app uses?
If not, is the intended position that fully functional custom builds from the public source tree are currently unsupported?
Thanks — I mainly want to keep my UI changes while using the normal OpenBubbles registration flow safely.