giseldo/neodataset huggingface dataset:
Spinner always on on user membership tab

<!---
Please read this!

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate.
--->

### Summary

When navigate to drawer/avatar/membership. The spinner is always on.

### Steps to reproduce

Navigate to drawer/avatar/membership. The spinner is always on.

### Platform information 

both

### What is the current *bug* behavior?

Spinner always on.

### What is the expected *correct* behavior?

Spinner off after loading.

### Relevant logs and/or screenshots

(Paste any relevant logs - please use code blocks (```) to format console output,
logs, and code as it's very hard to read otherwise.)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 2.0
Chore: Fix all unguarded route.params occurrences across entire code-base

<!---
Please read this!

The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate.
--->

## Goal

Fix all unguarded route.params occurrences across entire code-base.

## What needs to be done

Search all occurrences of the `route.params.` and replace them with `route.params?.` where applicable.

Some cases: `route.params.store, route.params.entity, route.params.comment, route.params.open, route.params.options, route.params.useForSelection, route.params.query, route.params.f, route.params.plus, route.params.group, route.params.source, route.params.noBottomInset, route.params.guid, route.params.index, route.params.goBack`

## QA

Require complete testing.

## UX/Design

N/A

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Weighted
- [ ] QA

Story points: 1.0
Portrait feed slowness

<!---
Please read this!

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate.
--->

### Summary

Investigate issues on the portrait feed performance and occasional failures to load the first time.

Possible problems: 
1. Seen posts are stored locally and the clean-up may not be working properly
2. Initial cached data

### Steps to reproduce

Initial failure (random): 
 - Log in for the first time to the app.

Slowness:
 - Possibly having a lot of seen posts stored locally (but it is just an assumption)

### Platform information 

both


### Possible fixes

We need to investigate the issue first in order to define

Story points: 3.0
Add ticker animation to live vote count



## Goal

Implement the ticket animation to the votes counter

## What needs to be done


Implement the ticket animation to the votes counter using reanimated (moti optional) 


## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

<!---
Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged.
--->


## Personas

More visible vote count change


## Experiments

none

## Acceptance Criteria

- [ ] Vote counter should animate while changing value

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 3.0
Missing onError check on Retryable image



### Summary

https://sentry.io/organizations/minds-inc/issues/2627157862/?project=1766867&query=is%3Aunresolved+user.id%3A1195393083806588938&statsPeriod=14d

### Steps to reproduce

- open an activity where the image doesn't exist

### Platform information 
Both

### What is the current *bug* behavior?

Throws undefined is not a function

### What is the expected *correct* behavior?

No error should be thrown and a media error message should be shown instead of the image

### Relevant logs and/or screenshots

https://sentry.io/organizations/minds-inc/issues/2627157862/?project=1766867&query=is%3Aunresolved+user.id%3A1195393083806588938&statsPeriod=14d

### Possible fixes

Check if onError is defined

Story points: 1.0
Improve component recycling by media type



## Goal

Improve performance and memory usage with the new recycler list by reusing the Activity components grouped by media type.

The first implementation just reuses the activity component for all posts, this will create and destroy Images and Video players depending on the post type. If we set the type by media, all posts with videos will be rendered using the same instances, reducing the creation and destruction of video players.

## What needs to be done

Redefine the FeedList's getType by activity media type

## QA

Videos should work as usual


## UX/Design

none

## Personas

General improvement of the UX

## Experiments
none


## Acceptance Criteria

- [ ] Videos should work as usual
- [ ] Check if there is issues by video playing recycling

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 1.0
Video component issues with new recycle feed



### Summary

The MindsVideo component doesn't support recycling. It has stable references to the entity passed so it doesn't change.

When an instance is recycled and rendered with other properties it plays the original video instead of the new one.

We need to refactor it to allow changing the entity and resetting all the video player properties and preloading.

### Steps to reproduce

- Scroll on the new feed implementation and some videos seem to be repeated.

### Platform information 
Both

### What is the current *bug* behavior?

Repeated videos on the feed

### What is the expected *correct* behavior?

The component should render the new video

### Relevant logs and/or screenshots

-

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 2.0
Bank Information: No validation error for incorrect phone number

### Summary

No error message is thrown when the phone number is invalid. 

### Steps to reproduce

1. Navigate to Wallet.
2. Navigate to Cash -> Add Bank Information. 
3. Enter invalid phone number.
4. Tap Save.
5. No error message appears.

### Platform information 

iPhone 13 - iOS 15

### What is the current *bug* behavior?

No error message is displayed. Just refreshes the current page and removes old phone number. 

### What is the expected *correct* behavior?

Error message must be displayed.

### Relevant logs and/or screenshots

![NoPhoneNumberValidationError](/uploads/1013f8f39cafe1279757a93f6dadf7a3/NoPhoneNumberValidationError.mov)

Story points: 2.0
Bank Information: Agree TOS checkbox is not available

### Summary

Bank Information page does not have a checkbox to select making it difficult for new users to understand how to accept TOS. 
This should be consistent with other TOS fields across the app. 

We need to solve the keyboard & scrolling issues

### Steps to reproduce

1. Go to Wallet.
2. Go to Add Bank Information page.
3. Scroll down and notice no checkbox available. 

### Platform information 

iPhone 13 - iOS 15

### What is the current *bug* behavior?

No checkbox shows up. Hard to figure where to click. 

### What is the expected *correct* behavior?

Checkbox should appear like in other places in app. 

### Relevant logs and/or screenshots

![image](/uploads/a0a9e00a08a4031f7ea1e35a75651b00/image.png)

Story points: 3.0
Bank Information: Inconsistent lines between fields

### Summary

The line spacing between fields looks inconsistent as some of them have more spacing than the other. 

### Steps to reproduce

1. Navigate to Wallet -> Cash.
2. Go to add bank information page.
3. Notice the line spacing between each fields. 

### Platform information 

iPhone 13 - iOS 15

### What is the current *bug* behavior?

Line spacing is weird. 

### What is the expected *correct* behavior?

Line spacing should match. 

### Relevant logs and/or screenshots

![image](/uploads/9541730bb5d6c66b27bd7543b7684b8a/image.png)

Story points: 1.0
Bank Information: Keyboard overlap on Countries field

### Summary

Keyboard is overlapping with countries field. 

### Steps to reproduce

1. Go to Bank Information page.
2. Select Country field. 
3. Opens a Country option menu.
4. Click on any other text field on page.
5. Both menus overlap.

### Platform information 

Browserstack iPhone 13 - iOS 15

### What is the current *bug* behavior?

Keyboard and Calendar menu is overlapping. 

### What is the expected *correct* behavior?

Keyboard and Calendar menu should not overlap. 

The Selector component should hide automatically when the keyboard is shown

### Relevant logs and/or screenshots

![image](/uploads/c086e2b8ce1687609a32062db998bb8d/image.png)

Story points: 1.0
See Latest Posts: arrow color inconsistency

<!---
Please read this!

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate.
--->

### Summary

![Screen_Shot_2022-07-18_at_18.12.15](/uploads/c2fd7d26ea366a68275d10bb560f2938/Screen_Shot_2022-07-18_at_18.12.15.png)

### Steps to reproduce

(How one can reproduce the issue - this is very important)

### Platform information 

(Browser, device, system stats, screen size)

### What is the current *bug* behavior?

(What actually happens)

### What is the expected *correct* behavior?

(What you should see instead)

### Relevant logs and/or screenshots

(Paste any relevant logs - please use code blocks (```) to format console output,
logs, and code as it's very hard to read otherwise.)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 1.0
Rotation lock is not working on iOS



### Summary

The rotation is not locked on iOS, most of the mobile screen should not allow rotation

### Steps to reproduce

rotate the device

### Platform information 
iOS

### What is the current *bug* behavior?

It is rotating and breaking the layout

### What is the expected *correct* behavior?

Should be locked

### Relevant logs and/or screenshots
![Simulator_Screen_Shot_-_iPhone_13_-_2022-07-18_at_12.19.37](/uploads/4bdff978b7a81f2e0050c8ccf8010ce0/Simulator_Screen_Shot_-_iPhone_13_-_2022-07-18_at_12.19.37.png)

### Possible fixes

check rotation manager

Story points: 2.0
Add Superminds to Wallet

<!---
Please read this!

The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate.
--->

## Goal

<!---
Clearly outline the goal of the issue and why we are doing it
--->
- Properly display all relevant information for Supermind transactions in the transaction ledger for both tokens and cash

## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->





## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

<!---
Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged.
--->


* A few small modifications will need to be made to the wallet.
  * Display SuperMind inbound/outbound payments within the transactions tab for both cash and token payment.
  * As much context and possible should be added.
* Example transaction lines [Transaction lines](https://www.figma.com/file/thrGepQAxmcMGB7MoEEckM/Supermind?node-id=430%3A12581)

---

* Todo - add info about Boost modal and boost console refactors.


## Personas

<!---
Who does this user impact and why (optional)
--->


## Experiments

<!---
Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined.
--->


## Acceptance Criteria

<!--
Everyone should be able to understand what is expected to be delivered
--->

- [ ] Wallet transaction items to reflect mockups

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 2.0
Introduce media attachments on Quote Posts

<!---
Please read this!

The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate.
--->

## Goal

<!---
Clearly outline the goal of the issue and why we are doing it
--->

Enable users to attach media to quote posts in V2 activity posts.

## What needs to be done

- Backend support for quote posts to have media attachments like regular posts (already supported via clipboard paste)
- Add media upload button / functionality to the composer for quote posts
- Display attached media above the quoted post in feed view
- Display attached media above the quoted post in single entity view

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->

Make sure to test link previews on twitter etc. 

## UX/Design Concepts

* [Design](https://www.figma.com/file/EkJej3mKP2lSzmWTLoqlXD/Minds-Design-System?node-id=1929%3A13000)

This is already accidentally supported by copy/pasting an image from the clipboard. Largely we want the front-end display the same, with a small change.

![image](/uploads/f6cb9389be47e241ed5b6edaec1cca2f/image.png)

We should add a 16px margin between the image and the quoted post.

![image](/uploads/77917e081642bc8917f2efbbda93b79a/image.png)

## Personas

- Core Minds users

## Experiments

n/a

## Acceptance Criteria

- [ ] When composing a quote tweet, the user is able to attach media (image, video) as they can with a normal post
- [ ] When the post appears in feeds, both the quoted post and the media attachment appear.

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 5.0
Remove Boost Offers from Boost Console and Modal

<!---
Please read this!

The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate.
--->

## Goal

<!---
Clearly outline the goal of the issue and why we are doing it
--->


## What needs to be done

- Remove the Offer tab from the boost console screen
- Remove the offer tab from the boost creation screen


## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

<!---
Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged.
--->


## Personas

<!---
Who does this user impact and why (optional)
--->


## Experiments

<!---
Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined.
--->


## Acceptance Criteria

<!--
Everyone should be able to understand what is expected to be delivered
--->

- [ ] ...

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 2.0
See latest post button component is affecting the touchables


### Summary

When the see latest post button is shown the user can't interact with the components behind or in top of it

### Steps to reproduce

- When the button is shown try to tap something on top of it

### Platform information 
Both

### What is the current *bug* behavior?

It is preventing the touchable below it to work

### What is the expected *correct* behavior?

It shouldn't affect other touchable

### Relevant logs and/or screenshots

![Simulator_Screen_Shot_-_iPhone_13_-_2022-07-14_at_17.47.36](/uploads/5e20231c87b77687213c2daf3a92fa3b/Simulator_Screen_Shot_-_iPhone_13_-_2022-07-14_at_17.47.36.png)

### Possible fixes

Ensure the container view ignores touches

Story points: 1.0
App Crashes sometimes when viewing stories

### Summary

App crashed on viewing stories.

### Steps to reproduce

1. Open minds app from cold state.
2. On Newsfeed home page, tap on the stories from minds.
3. On second story, app crashed immediately. 

### Platform information 

iPhone 11 Pro - v4.26

### What is the current *bug* behavior?

App crashed.

### What is the expected *correct* behavior?

App should not crash and be navigable to next story. 

### Relevant logs and/or screenshots

https://sentry.io/organizations/minds-inc/issues/3350544036/?query=release.version%3A4.26.0+os.name%3AiOS&statsPeriod=14d

![image](/uploads/b90dbce6de23188673ef9a9d55dfc488/image.png)

Story points: 2.0
Notifications scroll jumps when navigating back



### Summary

When navigating back to the notifications screen the UI freezes for a moment and the scroll jumps because the notifications are refreshed.

### Steps to reproduce

- Open the notifications screen
- Tap on a notification to open a post screen
- press back

### Platform information 

both

### What is the current *bug* behavior?

- Refresh the notifications

### What is the expected *correct* behavior?

- It should not refresh the notifications when navigating back

### Relevant logs and/or screenshots

![RPReplay_Final1657807091](/uploads/6becc0b40a393ffc12a69c5c4258e20c/RPReplay_Final1657807091.mov)

### Possible fixes

Remove the useFocusEffect and change the refresh logic of the screen. Maybe just refresh it when the tab is pressed

Story points: 2.0
Sentry: Cannot read property 'guid' of undefined (AnalyticsService#buildEntityContext)

<!---
Please read this!

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate.
--->

### Summary

https://sentry.io/organizations/minds-inc/issues/3348877448/?project=1766867&query=is%3Aunresolved&sort=freq&statsPeriod=14d

### Steps to reproduce

(How one can reproduce the issue - this is very important)

### Platform information 

(Browser, device, system stats, screen size)

### What is the current *bug* behavior?

(What actually happens)

### What is the expected *correct* behavior?

(What you should see instead)

### Relevant logs and/or screenshots

(Paste any relevant logs - please use code blocks (```) to format console output,
logs, and code as it's very hard to read otherwise.)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 1.0
Allow decimal in subscriber counts

### Summary

Currently, if you have 1100 subscribers, it will read 1k subscribers - I believe this happens until you reach 1500, which makes it read 2k (looking at existing examples).

It would be good if we could show this as 1.1k - at least in the lower thousands.

### Steps to reproduce

See a channel such as https://www.minds.com/bitman007
That has subscribers in the low thousands.

### Platform information 

Likely platform-agnostic, happening on the front-end.

### What is the current *bug* behavior?

We don't provide much definition on how many subs a user has when they first enter the thousands.

### What is the expected *correct* behavior?

Up for discussion. On the "about" page it shows the actual number - but on the user's channel, it doesn't. I personally think it should probably be to  1 decimal place - 1.1k / 1.2k up to 10000.

### Relevant logs and/or screenshots

Check front task https://gitlab.com/minds/front/-/issues/4792

### Possible fixes

Story points: 2.0
Comment push notification is not not opening focused comment



### Summary

When tapping a comment push notification the post is opened but it is not opening the comment bottom sheet.

### Steps to reproduce

Tap on a comment push notification

### Platform information 
both

### What is the current *bug* behavior?

it is not opening the comment bottom sheet

### What is the expected *correct* behavior?

it should open the comment bottom sheet and navigate to the correct comment

### Relevant logs and/or screenshots

(Paste any relevant logs - please use code blocks (```) to format console output,
logs, and code as it's very hard to read otherwise.)

### Possible fixes

The push now relies on the deep linking navigation and the focused urn params have a different name for the screen.

Story points: 2.0
Clear memory cache when switching users



## Goal
Optimize memory consumption removing data not longer needed

## What needs to be done

Add a memory cleaning when creating stores for a new user

## QA

- User switching should work correctly


## UX/Design

none


## Personas

General optimization that will improve the UX with multiuser

## Experiments

none

## Acceptance Criteria

- [ ] Should clear the cache when switching users
- [ ] It shouldn't affect multiuser functionality

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 0.0
Notification count badge seems inconsistent



### Summary

The badge seems inaccurate and the seen notifications are not taken in account

- [ ] Check if the seen notifications logic is in place and working correctly
- [ ] Remove the "Mark all as read" when we open the notifications screen
- [ ] make sure Activities in the feed are marked as read (the blue dot should get removed) when they were seen

Report:
"I constantly see 999+ notif orange badge on my app icon. When I go to the top of notifs they clear completely 
Seems inaccurate
Notifs are not detecting which you have looked at"

### Steps to reproduce

Open the app with a user that has many notifications

### Platform information 

Both (reported on Android)

### What is the current *bug* behavior?

Not taking into account the seen notifications

### What is the expected *correct* behavior?

It should discount the seen notifications of the badge

### Relevant logs and/or screenshots

-

### Possible fixes
-

Story points: 3.0
Mobile Automation: Add Settings test cases

## Goal
Similar to what we have in web, create tests for navigating to every settings page and validating the options available. 


## What needs to be done
Create tests for settings section. 


## QA
Test locally and on CI. 


## UX/Design
N/A


## Personas
N/A


## Experiments
N/A


## Acceptance Criteria

- [ ] Tests should work on both iOS and Android. 

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 2.0