← Back to Flaurral

Support & FAQ

Connect your Aurral server, explore your library, and keep the music moving. If an answer is not here, you can reach us directly.

Getting started

What is Flaurral?

Flaurral is a native iPhone client for an existing Aurral server. It brings Aurral discovery, library management, playlists, Flows, activity, and playback into a SwiftUI app. It does not install, host, or replace Aurral or Lidarr.

What do I need to use Flaurral?

You need an iPhone running iOS 26 or later and a reachable Aurral instance. Flaurral currently targets Aurral 2.7.

How do I connect my server?

Enter the complete HTTP or HTTPS address of your Aurral instance during onboarding. Add an API key if your server requires one. Flaurral also supports Aurral's OpenID Connect flow and temporary web sign-in for protected reverse proxies such as Authentik.

My server will not connect. What should I check?

Confirm that the address opens from the same device, includes the correct scheme and port, and points to Aurral rather than a Lidarr instance. Check that Aurral onboarding is complete and that the API key or proxy session is valid. HTTPS is recommended outside a trusted local network.

Library, Flows & playback

Can Flaurral manage my library and playlists?

Yes. You can explore canonical artists, albums, tracks, genres, favorites, and recent additions; manage library actions; work with static and shared playlists; and create or follow scheduled Flows and their download jobs.

Does playback work in the background?

Yes. Flaurral uses the native iOS audio stack with a persistent queue, background playback, Lock Screen and Control Center controls, interruptions, and AirPlay routing.

Why does Flaurral ask for microphone access?

The microphone is requested only when you choose Recognize Music. Audio is used temporarily with Apple's ShazamKit to identify the music playing around you. Flaurral does not record or keep the microphone audio.

Flaurral+

Do I need a subscription to use Flaurral?

No. The core Aurral, library, playlist, and playback experience remains available without payment. The optional annual Flaurral+ subscription supports continued development and unlocks hosted push notifications and display customization.

How are purchases managed?

Purchases are processed by Apple through the App Store and entitlement status is managed with RevenueCat. The price shown in the App Store applies. The annual plan renews automatically unless canceled through your Apple Account settings. You can restore an eligible purchase from Flaurral.

Read Apple's Standard EULA

What do push notifications require?

Push notifications require Flaurral+, notification permission, and an Aurral account able to update webhook settings. You choose which supported discovery, Flow, and album-request events Aurral sends.

Privacy & troubleshooting

Where are my credentials stored?

Your Aurral server address, API key, and applicable reverse-proxy session cookies are scoped to that server and stored in the iOS Keychain. They are not added to URLs or diagnostic reports. Disconnecting removes the stored connection.

How do I report a problem?

Please open a GitHub issue or email contact@nohit.dev. Include the Flaurral, iOS, and Aurral versions plus the steps that reproduce the problem. Never include API keys, passwords, cookies, or other credentials.

Where can I read the Privacy Policy?

The full policy is available on the Privacy Policy page.

Contact support

Include your app version, iOS version, Aurral version, and a short description of what happened.

Email supportOpen GitHub issue