We discovered a new bug in app version 0.4.40 for iOS: when onboarding a base the app will show a screen with "Connection failed" and "We failed to connect to your Base."

We're currently working on a fix and will release an update soon.

Possible workarounds are: using an Android device to onboard your Base or use a previous app version to onboard

Our development team is working on a fix. We are sorry for the inconvenience.

Root cause: Firmware bug

Solution: The Base's battery is good for 2+ weeks. Please use unplugged.

Root cause: Notifications are not working for all users on Android 14 devices, across multiple models (such as Pixel 7 Pro, Pixel 7a, Motorola Razr+ 2023). The exact cause is still unknown but the issue appears to be Android 14-specific and affects notifications both within and outside the FluentPet app. Earlier Android versions and iOS device are unaffected.

Solution: This issue is under active investigation and will be fixed in a future app update.

Notes: As this issue is affecting all Android 14 users, we recommend focusing on temporary workarounds while the development team works on a solution. Further updates are expected in upcoming app versions, and affected users are encouraged to report their experiences to help with troubleshooting.

Root cause: a race condition is present in the app code where 2 requests are sent at the same time to the Base, if one is processed before the other, the Base would never try to register with the FluentPet servers and onboarding would fail. Retrying the onboarding process would usually eventually fix the issue.

Solution: This issue was fixed in app version 0.4.37 and above.

Root cause: custom VPN or DNS configuration by "Amazon Shopper Panel" app.

Solution: Remove the Amazon Shopper Panel app temporarily while you attempt the onboarding process. You can re-install it after the setup.

Notes: The Amazon Shopper Panel app uses a custom DNS that filters your traffic and prevents the Base from communicating with the phone while connected to the Base's local intranet. If you disable the ad verification option in the app this might work as well. You can also check that you do not have any other custom DNS settings on your phone.

Root cause: Server implementation bug: Sorting buttons by most used is taking very long (several seconds to minutes) in case the account has several thousand presses. (solved in new backend version)

Solution: now fixed

Workaround: The way Buttons are sorted in between sessions is stored, so selecting a different sorting method, like A-Z will make sure the app loads faster.

Root cause: Currently unknown

Solution: Verify that the Button is lighting up Blue when pressed. Try re-linking the Button with the Base. Try plugging and un-plugging the Base in a charger. Press the Base Button (enter sync mode), wait 3 seconds, then press the Base Button twice (cancel sync mode). If after these steps the Base is still not responding, contact the FluentPet team <info@fluent.pet>

Notes: The Base should play a sound when entering sync mode and show the Sync mode LED (blue), then the LED should turn off when you double-press to cancel.

Root cause: Base firmware issue

Solution: resolved in new Base firmware

Root cause: Button firmware bug (solved in newer versions)

Solution: upgrade your Button firmware

Root cause: Bug in Base firmware

Solutions: (1) Contact the FluentPet team <info@fluent.pet> to manually trigger to unstick (includes 12 hour delay), or (2) allow your Base battery to fully drain (i.e. don't plug it in until it dies)

Root cause: ~2% of Bases were upgraded to an intermediate Firmware version with a bug (solved in newer versions).

Solution: factory reset and relink buttons

Root cause: Button firmware update bug (solved in newer versions)

Solution: remove the battery from the last Button linked, put it back in, and try one more time.