Testing MedBuk
Install a MedBuk testing build and share useful feedback.
Use MedBuk Preview when the team invites you to try an early version. It is a separate app with a separate testing account. Use sample entries while testing.
How do I install it?
Ask the MedBuk team for the current installation card, then open the link for your phone or scan its QR code. Android testers download the app from that link. iPhone testers must register their device with the team before its Preview build is prepared.
For a wider test, MedBuk Beta will be distributed through Apple TestFlight or a Google Play testing invitation. These invitations become available after setup and build approval; they are not public store releases.
The earlier iOS development build needs a developer connection. It is not the Preview app. New Preview installation links are still pending.
What if the team cannot prepare my iPhone build?
Device registration, Apple's signing step and the finished build are separate steps. The team must complete all three before sending an installation link. A setup failure does not mean your iPhone registration was lost.
The build tools now report which setup check failed and can check the testing server without starting another build. If you are helping with setup, share the error category with the team. Enter Apple passwords and verification codes privately on your device. Keep using the team's confirmed installation link; the old development app needs a developer connection and cannot substitute for Preview.
How do I report an issue?
Open You → Details and include the app version, build number and testing app name. Describe the screen and the action that failed. Do not send passwords, login codes or photos of personal health records with your report.
How will I receive changes?
Some compatible changes arrive when you reopen the testing app. If a change needs a new installation, the team will provide a new link. Preview updates stay in the testing app; production releases follow a separate approval process.