Resolve Incorrect Update Prompt (2.200) After Installing 2.570

In some cases, the Minn Kota Fishing App may incorrectly display a prompt to install software version 2.200 even after the motor has already been updated to a newer version (such as 2.570).

This is an app display issue, not a failed update.

Restarting the app and power cycling the motor will typically resolve the issue.

When This Happens

You may experience this issue if:

  • The motor has already been successfully updated to 2.570
  • The app still suggests installing 2.200
  • The motor appears to be functioning normally otherwise

This behavior has been identified as intermittent and likely related to app/backend sync issues, not a widespread software failure.

Resolution: Restart the App and Power Cycle the Motor

Follow these steps to clear the incorrect update prompt:

Step 1: Turn Off the Motor

  • Power the motor completely off

Step 2: Force Close the Minn Kota Fishing App

  • Close the app fully (do not leave it running in the background)
    • On iOS: Swipe up and remove the app
    • On Android: Force close from the app switcher

Step 3: Power the Motor Back On

  • Turn the motor back on and allow it to fully initialize

Step 4: Reopen the App

  • Launch the Minn Kota Fishing App again
  • Allow it to reconnect to the motor

Expected Result

  • The incorrect 2.200 update prompt should no longer appear

This process has been confirmed to resolve the issue in real-world cases.

Why This Works

  • The app can occasionally display outdated update recommendations due to:
    • Cached app data
    • Temporary backend synchronization issues
  • Restarting the app forces a fresh sync with the motor and update server

If the Issue Persists

If the prompt still appears after completing the steps above:

  • Confirm the motor software version in the app
  • Ensure:
    • The app is fully up to date
    • Your phone OS is current
  • Repeat the restart steps once more

Agent Notes

  • Do not advise reinstalling 2.200 if 2.570 is already installed
  • This is not a downgrade requirement in this scenario
  • Use this as a first-line resolution before escalation
Was this article helpful?
0 out of 0 found this helpful

Articles in this section