ran the migration on a release build, confirmed that I was not entering `handleReduxMigrationFailure`.
Additionally logged the following in `native/components/community-actions-button.react.js` and got these results:
```
const canManageFarcasterChannelTags = useThreadHasPermission(
community,
threadPermissions.MANAGE_FARCASTER_CHANNEL_TAGS,
);
console.log('canManageFarcasterChannelTags', canManageFarcasterChannelTags);
```
{F2050415}
(I am an admin of comm supporters and a personal test community so I expected to have two `true` values here)
Additionally did one final test to confirm that users were not forcefully being logged out due to the failed migration:
1. `arc patch D12503` (this is the last diff for this stack)
2. `git checkout mobile-v1.0.354`
3. Removed `native/facts/authoritative_keyserver.json`
4. `yarn cleaninstall`
5. Delete the app from iOS simulator
6. Do an iOS release build to iOS simulator
7. `git checkout arcpatch-D12503`
8. `yarn cleaninstall`
9. Do an iOS release build to iOS simulator
Confirmed I got no "redux migration failure" logs (added this log to `native/redux/handle-redux-migration-failure.js` just like in this [[ https://gist.github.com/Ashoat/96185c545cd1d2853e2f534dd74ff8dc | patch ]]).
Also when I did the new release build after following all the steps, I was not logged out of the app, and was able to confirm that I could manage farcaster channel tags for communities that I am an admin in