giseldo/neodataset huggingface dataset:
Unable to manage tags

### Summary

User kajinoko is unable to manage tags in Discovery, experiencing fatal error. User also cannot scroll their tags in a list, and cannot scroll horizontally through quick tags while posting. Reinstalling the app has not helped.

### Steps to reproduce

Discovery>Manage Tags>Add

### Platform information 

Google Pixel, Android 11; replicated on Samsung Note 10, Android 9

### What is the current *bug* behavior?

![Screenshot_20211223-085658](/uploads/b154f9430d022edaebee460cafb4c377/Screenshot_20211223-085658.png)

### 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: 3.0
Onboarding navigation broken

<!---
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

(Summarize the bug encountered concisely)

### 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
Divider line between stories and feed is too thick

Shouldn't this be a thin line? It looks blocky.

![Screenshot_20220117-124227_Minds](/uploads/d962078621987128f6204a4690c05b1d/Screenshot_20220117-124227_Minds.jpg)

![Screenshot_20220117-124224_Instagram](/uploads/a3767ec0972a4cafae1bb128007b868e/Screenshot_20220117-124224_Instagram.jpg)

Story points: 1.0
Notifications refresh 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

When refreshing notifications it is randomly showing old results.

### Steps to reproduce

- Create votes and comments to generate notifications
- Refresh the list on mobile many times
- new notifications should be shown and disappear randomly

### Platform information 
Both

### What is the current *bug* behavior?

It is showing old versions of the notifications list randomly

### What is the expected *correct* behavior?

It should always show the latest notifications

### 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

Probably related to useApiFetch hook

Story points: 3.0
Dot indicator it's misplaced on the notifications tab icon


### Summary

Misplaced notification dot indicator


### Relevant logs and/or screenshots

![Screen_Shot_2022-01-18_at_15.44.09](/uploads/9d6f1c80b5e6eeabec8a5510f9d63d17/Screen_Shot_2022-01-18_at_15.44.09.png)

Story points: 1.0
Comment input closes the bottomsheet on Android


### Summary

If the user closes the bottom sheet by swiping down while the comment input is visible. The bottom sheet will fail to open the next time.

### Steps to reproduce

 - Tap on the comment icon in a post
 - Tap add comment
 - Close the bottom sheet by swiping down
 - Tap again on the comment icon to open the comments again. 
   The bottom sheet opens but it is closed down immediately 

### Platform information 
Android

### What is the current *bug* behavior?

Close the bottom sheet on the next open

### What is the expected *correct* behavior?

It shouldn't affect the functionality

### Possible fixes

Hide the input when the bottom sheet is closed

Story points: 3.0
Update react-native-vision-camera and disable frame processors

<!---
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

Update react-native-vision-camera and disable frame processors to improve performance and build time. 

We are not using frame processors at the moment so this will not brake any functionality

Story points: 5.0
Group search is not working on mobile



### Summary

No results are shown when searching groups on mobile (Discovery search)

### Steps to reproduce

- Search for some common word and select the group tab on discovery

### Platform information 

Android and iOS

### What is the current *bug* behavior?

Not results shown

### What is the expected *correct* behavior?

It should show the same results as the web

### Possible fixes

Check endpoint and parameters to replicate web functionality

Story points: 0.0
Small navigation related refactors

@msantang78 - navigation is looking great. Just two small areas to address, then we should be all good.

- [x] Please remove the animation currently present on the menu screen. We can create a future task to add refined navigation animation in the future, but for now I'd be happy to simply remove it.

- [x] The height of the lower nav bar should be modified to better match the designs here. Currently it's a little short, and the buttons are very low. See below.

- [x] Can you please increase the size of the search and chat icons in the header, to better match the designs below. They are currently on the small side.

https://www.figma.com/proto/EkJej3mKP2lSzmWTLoqlXD/Minds-Design-System?node-id=60%3A84&scaling=scale-down&page-id=60%3A83

Story points: 2.0
Password visibility should be added for all textboxes with password

### Summary

This is an improvement request that any passwords entered across the application should have the eye button to hide/show password. This can be extremely helpful when user enters a typo in the password and can fix it easily rather than retyping the entire password. 

### Steps to reproduce

1. Navigate to Minds.
2. Go to Change Password page or any other page where password is entered in a textbox.

Notice that no eye icon exists to see the password.

### Platform information 

Android & iOS

Story points: 2.0
Navigation issues from comments and other bottom sheets


### Summary

When navigating from some bottom sheets the screen is opened behind it.

(reported by @manishoo)

### Steps to reproduce

Open vote interaction modal and tap in a channel

### Platform information 

Android and iOS

### What is the current *bug* behavior?

The channel is opened behind the bottom sheet

### What is the expected *correct* behavior?

The channel should be opened on top of the bottom sheet

### Relevant logs and/or screenshots

![Untitled](/uploads/500fc0b0ac9de4d9c3a421e83b5f1b8d/Untitled.mov)

Story points: 3.0
Comment input not visible


### Summary

Comments input is behind the comments bottom sheet

### Steps to reproduce

 - Open the input to create a new comment
 - The input should be shown but is not visible
 - Close the bottom sheet and the input is visible behind

### Platform information 

Android and iOS

### What is the expected *correct* behavior?

The input should be on top of everything

### Possible fixes
The bottom sheet uses teleport to render the modals on the main screen. We need to use the same (Maybe the floating input that I implemented)

Story points: 3.0
(bug) Images | Weird aspect ratio when opening images

I found out while testing the https://gitlab.com/minds/mobile-native/-/issues/4030, some pictures seem to have wrong ratio.

The sushi picture I open in the video has ratio of 1:1 but on phone it's squished. Same with the meme I open later, it should almost take full screen, but it's really squished.

It also doesn't seem to be working on all pictures. I tried some of photos made by ishiyo, and they were showing properly.

![untitled](/uploads/c4a164ad911633e0bf3b78135cfd0ed8/untitled.mp4)

## Tested on
- I have android .apk version

Story points: 3.0
Create a 4.20.1 patch build

### Summary

Cherry-pick the fixes for the following issues and create a patch build.

https://gitlab.com/minds/mobile-native/-/issues/3994 \
https://gitlab.com/minds/qa/qa/-/issues/153 \
https://gitlab.com/minds/mobile-native/-/issues/4014 \
https://gitlab.com/minds/mobile-native/-/issues/4007

Story points: 0.0
Finish new navigation implementation



### Summary

Most of the implementation was done in order to have a demo but there are some extra tasks we need to do in order to complete the refactor.

- [x] Move navigation types with params to each navigator (Newsfeed, Discovery, More)
- [x] Show number on the chat icon and remove the old implementation
- [x] Check/Fix deep linking
- [x] Check/Fix notification navigation
- [x] Fix typescript errors
- [x] Fix spec tests
- [x] code clean up

:warning: This task is necessary if we decide to move forward with the refactor

Story points: 8.0
Create a POC for running Mobile Automation on Real Devices


### Summary

This task covers creating a working automation test case for mobile application that tests the application on a real device. It will include researching out other options available apart from Browserstack. 

Some work on WebdriverIO + Browserstack has already been done. Compare if we can find anything better that provides stable automation across real devices.

End Result: 
- Working login test case as an example on a real Android and iOS

Story points: 8.0
Remove APK from browserStack once merged and on branch update

<!---
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

We should delete the APK from BrowserStack once the MRs are merged in. In order to reduce the list size

Also, because BrowserStack allow to have multiple files with the same name, we should delete the previous file if it exists

Frontend: https://gitlab.com/minds/front/-/blob/master/.gitlab-ci.yml#L252

Story points: 3.0
Datetime picker is selecting the day before when you tap on the calendar

<!---
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
The date picker is selecting the day before the one selected by the user

### Steps to reproduce
Open the composer and go to the scheduler options
Select a date from the calendar and it selects the day before (Probably due to timezone)

### Platform information 

Android and iOS

Story points: 2.0
Refined toaster notifications for mobile

See below revised toaster notifications for mobile:

Revised Designs:
- https://www.figma.com/file/EkJej3mKP2lSzmWTLoqlXD/Minds-Design-System?node-id=671%3A4120
- https://www.figma.com/file/EkJej3mKP2lSzmWTLoqlXD/Minds-Design-System?node-id=671%3A4307 
- https://www.figma.com/file/EkJej3mKP2lSzmWTLoqlXD/Minds-Design-System?node-id=675%3A4226
- https://www.figma.com/file/EkJej3mKP2lSzmWTLoqlXD/Minds-Design-System?node-id=671%3A4079
- https://www.figma.com/file/EkJej3mKP2lSzmWTLoqlXD/Minds-Design-System?node-id=671%3A4019

Story points: 5.0
[GAT-MDS-7-1] Unable to connect the Wallet due to phone verification flow failure.

Component:
Wallet

Steps to reproduce:
Launch the app.
Login to the account.
Tap the "Wallet" icon on the top right of the screen.
Tap the "Connect Wallet" button.
Type the "2408011889" in the "Phone Number" input field.
Tap the "Send Verification Code" button.
Type in the confirmation code from SMS.
Tap the "Confirm" button.
Observe the "Phone Verification" screen. 

Severity:
High

Attachments:
https://tracker.testerwork.com/image_files/a6bbbc732e1531002f370dea96631afe72ebea99f54e0a7a4ca16a7433523718566521dfaa6273f4710fdb9db31d7189, https://tracker.testerwork.com/video_files/ec126509310b1722a133b0abf2a4952c68d16726d3e5e111e421c71bbfa97c9867920402c98550b3330e3fa007b6062f, https://tracker.testerwork.com/video_files/952c9fca8e0d57920f00a1bd0749ede14c6a394cf9631f1abc0629e45aff60018c03e99bb1670f7ceb78625c9074a057

Test case id:


Country:
United States

Description:
Actual results
The phone verification is failed.  
Nothing happened after 2 attempts. And about 10 minutes later, the reminder message "Please connect your wallet"  was displayed.

Expected results
The phone verification is completed, and the wallet is connected. 



Environment:
platform_info: Samsung Galaxy S21 Ultra, Android 12.0 12
operating_system: -
mobile_device_name: Samsung Galaxy S21 Ultra
web_browser_and_version: -
operating_system_version: Android 12.0 12

Credentials:


Repro rate x5 1:

Story points: 3.0
(Bug) 4.20.1 Notifications | Notifications loading improperly

Users pointed out that the notifications aren't loading in 4.20 [here](https://www.minds.com/newsfeed/1317494592077041667)

I tested it, and when I pull down the notifications to reload, it won't load new messages, but if I switch to different category, they load.

![Example of the video](/uploads/626b6d656d55aa3756e809564b4cc931/vidma_recorder_14122021_163045.mp4)

Story points: 3.0
Update 4.20.0 changelog

<!---
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

(Summarize the bug encountered concisely)

### 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
Stuttering on the filter gallery(Android)

<!---
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

Due to the flat list implementation on Android that has the removeClippingSubviews on by default, that the filters are slow, and a repeated scroll event bug. The Filter gallery has a lot of stuttering/glitches on android.

Story points: 2.0
Discovery: Add "Top" tab (mobile app)

In order to improve the quality of content on the Discovery page, and to drive engagement to our top content, we want to:

1. Add a new `Top` tab  to the Discovery page.
2. Use the feed powering the Guest Mode homepage to present posts in this `Top` feed.
3. Make `Top` the default tab when clicking the `Discovery` button in the Minds navigation.

Quick mock to illustrate:

![image](/uploads/51b51050d468b7edae4d5f52a1ba5c03/image.png)

- [ ] Follow experiment https://gitlab.com/minds/minds/-/issues/2869

Story points: 3.0
Native crash with new version of snowplow


### Summary

FATAL EXCEPTION: OkHttp Dispatcher

java.lang.NoSuchMethodError: No virtual method toString(Z)Ljava/lang/String; in class Lokhttp3/Cookie; or its super classes (declaration of 'okhttp3.Cookie' appears in /data/app/~~YJO4_d2gHDNHk5P7_Ij8KQ==/com.minds.mobile-3lh7hgD_FNNolArskC8Muw==/base.apk!classes5.dex)

FATAL EXCEPTION: OkHttp Dispatcher
Process: com.minds.mobile, PID: 30202
java.lang.NoSuchMethodError: No virtual method toString(Z)Ljava/lang/String; in class Lokhttp3/Cookie; or its super classes (declaration of 'okhttp3.Cookie' appears in /data/app/~~YJO4_d2gHDNHk5P7_Ij8KQ==/com.minds.mobile-3lh7hgD_FNNolArskC8Muw==/base.apk!classes5.dex)
	at okhttp3.JavaNetCookieJar.saveFromResponse(JavaNetCookieJar.java:45)
	at com.facebook.react.modules.network.ReactCookieJarContainer.saveFromResponse(ReactCookieJarContainer.java:37)
	at okhttp3.internal.http.HttpHeaders.receiveHeaders(HttpHeaders.kt:207)
	at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.kt:85)
	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
	at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.kt:76)
	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
	at okhttp3.internal.connection.RealCall.getResponseWithInterceptorChain$okhttp(RealCall.kt:201)
	at okhttp3.internal.connection.RealCall$AsyncCall.run(RealCall.kt:517)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
	at java.lang.Thread.run(Thread.java:923)

### Steps to reproduce

Log in with a user and it crashes after the request

### Platform information 
Android

Story points: 2.0
Social Compass Mobile: No confirmation message that the questionnaire was submitted

### Summary
When you submit the social compass questionnaire, there is no confirmation message that it has been successfully submitted.

### Steps to reproduce
1. Login to Minds.
2. Open the Social Compass from the Newsfeed page.
3. Answer all the questions.
4. Hit Save button.

### Platform information 
All web and mobile platforms

### What is the current *bug* behavior?
Currently, just navigates back to Newsfeed page.

### What is the expected *correct* behavior?
Confirmation text must appear when the questionnaire is submitted.

Story points: 1.0
Comment push notifications don't always redirect to the relevant question

See steps below on replicating this issue.

- View comments on a given post
- Close the app
- When a new comment notification is received, tapping on it opens the app, but the redirection never happens.
- Also after receiving a push notification on an upvote, the direction never happens. The user simply remains on the original comment thread.

Please see video below.

![RecordIt-1638275199](/uploads/6fa81f8fc5f1cf2074364c75c139ec70/RecordIt-1638275199.MP4)

Story points: 3.0
typo in social compass

<!---
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

(Summarize the bug encountered concisely)

### 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: 0.0
Seems like comments sockets are not working

<!---
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

(Summarize the bug encountered concisely)

### 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: 0.0
(bug): Pressing the "check for updates" button in the iOS app does nothing.

<!---
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

(Summarize the bug encountered concisely)

### Steps to reproduce

1. Press "Settings"
2. Press "Check for updates"

### Platform information

iOS 12.1 / iPhone SE

### App version

3.2.0

### What is the current *bug* behavior?

Pressing the "check for updates" button in the iOS app does nothing.

### What is the expected *correct* behavior?

Pressing the "check for updates" button should actually check if there's an update and if there is, allow the user to install it. If not, it should let them know that the app is up to date.

### 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
(bug): push notif to conversation reply has typo and doesn't properly direct

<!---
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

(Summarize the bug encountered concisely)

### Steps to reproduce

(How one can reproduce the issue - this is very important)

### Platform information

(Device, Android/iOS version, system stats, screen size)

Android latest

### App version

(App version and build number)

3.2.0

### What is the current *bug* behavior?

(What actually happens)

directs to wrong place in conversation thread and push notif SHOULD say what the regular notification says "username replied to your comment on x"

### 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.)
![Screenshot_20190305-124008_Contacts](/uploads/8c9c35fc2b73507c1798636c056b14f9/Screenshot_20190305-124008_Contacts.jpg)
![Screenshot_20190305-125144_Minds](/uploads/b2ef724caab8bdcdc06d05081ca9b9f8/Screenshot_20190305-125144_Minds.jpg)
### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 2.0