-
-
Notifications
You must be signed in to change notification settings - Fork 23
How to build it?
Alexander Kopachov edited this page Feb 5, 2024
·
5 revisions
Pull the repo with recursive submodule initialization and then run ./build.ps1
command to build the app. Once done archives with all the necessary .FAP and .FAL files will be available in the build
directory.
Just in case if you would like to build not via ./build.ps1
file then you have to revise totp/features_config.h
file and ensure that this line #define TOTP_TARGET_FIRMWARE TOTP_FIRMWARE_XTREME_UL
targets your firmware. If it is not, then you have to update this line by changing it to #define TOTP_TARGET_FIRMWARE TOTP_FIRMWARE_OFFICIAL_STABLE
or #define TOTP_TARGET_FIRMWARE TOTP_FIRMWARE_OFFICIAL_DEV
, depends on target firmware you are building app for.
- Home
- First steps
-
FAQ
- How does it work?
- Is it secure?
- How to get it?
- How to build it?
- Where is config file?
- What is token secret and where to get it?
- Is there a CLI?
- Is there a token input automation?
- How to add new token?
- Does it support Steam-style tokens?
- How to change\recover PIN?
- How to backup?
- How to reset application?
- Flipper Authenticator generates invalid codes, why so?
- How to migrate from another authenticator app?
- TOTP codes became invalid after daylight saving time switch, why?
- Is it possible to connect "Flipper Authenticator" and "Bluetooth Remote" apps to the same device via Bluetooth?
- What does "API version mismatch" error mean?
- Does it support AZERTY\QWERTZ keyboard layout?
- Is there a companion app for desktop?
- Is it possible to migrate to another authenticator app?
- Why it is not listed in official Flipper Application Catalog?