giseldo/neodataset huggingface dataset:
Android full version keep updating for 4.35.0

<!---
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)

Android full version keep updating for 4.35.0

### Steps to reproduce
- download full version
- you'll be prompted to update.
- after update you'll be prompted to update

(How one can reproduce the issue - this is very important)

### Platform information

(Device, Android/iOS version, system stats, screen size)
- Android full version

### App version

(App version and build number)
4.35.0

### What is the current *bug* behavior?

(What actually happens)
Android full version keep updating for 4.35.0

### What is the expected *correct* behavior?

(What you should see instead)
Android full version should not keep updating for 4.35.0

### 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
Videos disappear from feed after upload

### Summary

After a video is uploaded and the page is refreshed, the video seems to disappear from the channel feed.

### Steps to reproduce

desktop:
- upload video
- refresh page
- additionally, you may try the filter tool to find the video; initially this worked for me but did not work on subsequent attempts

mobile:
- upload video
- refresh
- once again filtering may be tried but this never worked for me on mobile

### Platform information 

windows 11, google chrome; android 12

### What is the current *bug* behavior?

after the user refreshes, the video seems to just disappear as though it were made unlisted. post can still be found if the user has the link.
- desktop, https://drive.google.com/file/d/1GnZMFK4Jwy25D-KAZLY6Dlod4RiY5-zm/view?usp=share_link

- mobile

![XRecorder_01052023_115704](/uploads/ccd8ddaf888598a410aea94037943927/XRecorder_01052023_115704.mp4)

### 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
Store release - 4.35.0 - Android and iOS

<!---
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
--->
Store release - v4.35.0


## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->
Run a smoke test and review all already tested tasks from staging environment.

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->
- store release for Android and iOS

## UX/Design

<!---
Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged.
--->

## Mobile

<!---
Does a mobile card need to be created? Any notes for mobile?
--->

- [ ] Is Mobile Required?

## 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: 1.0
Multi-image closes composer

### Summary

Attempting to upload a multi-image causes composer to close entirely.

### Steps to reproduce

attempt to upload a multi-image

![XRecorder_26042023_131209](/uploads/d9799120118dcc57b8dccba8e5e281da/XRecorder_26042023_131209.mp4)

### Platform information 

- Galaxy Note 10, Android 12
- Android 13

### What is the current *bug* behavior?

Composer closes, post is discarded

### 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
Remove navigation to Payment Method screen for Google Play version

<!---
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

Remove navigation to the Payment Method screen for the Google Play version

<!---
Clearly outline the goal of the issue and why we are doing it
--->

## What needs to be done

Remove navigation to the Payment Method screen for the Google Play version

<!---
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
--->
- switch experiment toggle and test composer default


## UX/Design

<!---
Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged.
--->

![image](/uploads/0c60dc9a0fd8827cace50712d7109ac4/image.png)


## Mobile

<!---
Does a mobile card need to be created? Any notes for mobile?
--->

- [ ] Is Mobile Required?

## 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
Show the backend error messages in the in-app verification



## Goal

Display the error messages sent by the server when verifying a user. 


## What needs to be done

If the server response includes an error message show it to the user


## QA

- Enable in-app verification FF
- Go to in-app verification
- intentionally write a wrong code
- run verification
- a message should be shown


## Experiments

-

## Acceptance Criteria

- [ ] a message should be shown if the code verification fails

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 2.0
Update the checklist of the task for DOR

<!---
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

- Update Gitlab template to match mobile needs.
- Update the checklist of the task for DOR. 
- Review the entire template

<!---
Clearly outline the goal of the issue and why we are doing it
--->


## What needs to be done

Add native build for android both play and full and build and testflight for iOS in CI on any branch.

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->


## QA

https://gitlab.com/minds/gitbot-issue-policies/-/merge_requests/2

<!---
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.
--->

## Mobile

<!---
Does a mobile card need to be created? Any notes for mobile?
--->

- [ ] Is Mobile Required?

## 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: 3.0
Boosted content title should not be shown on the main feed



### Summary

The boosted content title is shown in the main feed

### Steps to reproduce

Open the the app

### Platform information 

both

### Relevant logs and/or screenshots

![imagen](/uploads/4f420c31838c527ef49f8ac3989ef7c1/imagen.png)

### Possible fixes

TBD

Story points: 2.0
Hide referrer banner and create a banner for wefounder



## Goal

Hide the referrer banner and add one for the wefounder campaign


## What needs to be done

Add FF and create a new banner


## QA

-

## UX/Design
-


## Experiments

Add one FF for referrer and other for wefounder


## Acceptance Criteria


- [ ] Banners should be controlled by FF
- [ ] Wefounder should be visible

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 2.0
Cant add multiple images

<!---
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

Cant add multiple images via gallery

### Steps to reproduce

1. Open composer
2. Upload an image
3. Try uploading another image

Alternatively 

1. Open composer
2. Upload multiple images
3. See there is only one uploaded

### Platform information 

Android, 4.34.1

### What is the current *bug* behavior?

App does not let you upload multiple images (can upload more images with camera)

### What is the expected *correct* behavior?

Second picture should be added to composer

### Relevant logs and/or screenshots

x

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 3.0
Add button for "delete tier" under memberships

<!---
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

Add button to delete memberships.
Here is the membership page currently:
![Screenshot_20230413-173725_Minds](/uploads/58b3020acd3537e90ccf7c6404f8f506/Screenshot_20230413-173725_Minds.jpg)


## 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.
--->

## Mobile

<!---
Does a mobile card need to be created? Any notes for mobile?
--->

- [ ] Is Mobile Required?

## 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
Supermind reply notification takes user to the supermind question, not result

<!---
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

Supermind reply notification takes user to the supermind question, not result

### Steps to reproduce

1. Supermind someone
2. Get reply
3. Click notification
4. See that you are redirected to 

### Platform information 

iOS, 4.34.0

### What is the current *bug* behavior?

Supermind reply notification behaving wrong

### What is the expected *correct* behavior?

Supermind reply should go to supermind reply

### Relevant logs and/or screenshots

![Video](/uploads/48cc0b373cb11a477915e94165f2da3c/Video.mp4)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 2.0
Uploading image into comments causes app to crash

### Summary

When an image is uploaded as a comment, the app immediately crashes

### Steps to reproduce

1. Find a post
2. Try commenting a picture
3. See the app crashes

### Platform information

Android (does not happen on iOS)

### App version

4.34.0

### What is the current *bug* behavior?

app crashes when attempting to upload image in comments

### What is the expected *correct* behavior?

app should upload image to comments

### Relevant logs and/or screenshots

![XRecorder_12042023_132756](/uploads/eb6c1bc76e31e3dff315772e69ccb6ae/XRecorder_12042023_132756.mp4)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 3.0
Width/Height are inverted on images picked on Android



### Summary

Width/Height are inverted on images picked on the gallery (Android)

Seems to be an expo image picker issue https://github.com/expo/expo/issues/22097

### Steps to reproduce

pick a rotated image on android

### Platform information 

android

### What is the current *bug* behavior?

The preview in the composer is showing the wrong aspect ratio

### What is the expected *correct* behavior?

Image should be displayed correctly

### Relevant logs and/or screenshots

![imagen](/uploads/7c0c967f507235c1801635e221353001/imagen.png)

### Possible fixes

TBD

Story points: 2.0
Add Back button to all screens in the drawer

<!---
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

Make the navigation in drawer consistent by adding the back button to the screens missing it.
- Wallet
- Analytics
- Groups
- Settings

<!---
Clearly outline the goal of the issue and why we are doing it
--->


## What needs to be done

Add back button to the screens:
- Wallet
- Analytics
- Groups
- Settings

<!---
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
--->

Check for all screens the back button exists and working.


## UX/Design

<!---
Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged.
--->

- Use same icon and position as per the Boost or Supermind screens.

## Mobile

<!---
Does a mobile card need to be created? Any notes for mobile?
--->

- [ ] Is Mobile Required?

## 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: 3.0
Boost channel in-feed notice does not go away

<!---
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

Boost channel in-feed notice does not go away

Extend the scope to make sure all in-feed notices are dismissible.

### Steps to reproduce

1. Have in-feed notice in the feed
2. Try dismissing it by clicking Learn More
3. Try dismissing it by clicking Boost Now
4. See that neither worked

### Platform information 

iOS, 4.34.0

### What is the current *bug* behavior?

The in-feed notice stays, even after boosting the channel.

### What is the expected *correct* behavior?

The notice should go away if:
1. User clicks Learn More
2. User clicks Boost Now

### 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
Boost partners: served_by_guid parameter + analytics

<!---
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 boosts on channel screen are not being counted as boost partner boosts and boost settings is not taking effect

### Steps to reproduce

(How one can reproduce the issue - this is very important)

### Platform information 

All

### What is the current *bug* behavior?

- channel boosts are not counted as boost partner boosts
- analytics for channel boosts aren't correct
- safe/unsafe settings doesn't take effect on channel boosts

### What is the expected *correct* behavior?

the opposite of above

### Relevant logs and/or screenshots

N/A

### Possible fixes

use the `served_by_guid` parameter

Story points: 3.0
Images uploaded via mobile are stretching horizontally

### Summary

Title. See example posts

### Steps to reproduce

Upload multi-image via mobile
https://www.minds.com/newsfeed/1490792788223070209
https://www.minds.com/newsfeed/1490411508868321294

### Platform information

- Note 10, Android 12 - IT HAPPENS :heavy_check_mark: 
- Nokia 4.2 Android 11 - IT HAPPENS :heavy_check_mark: 
- Honor 9 Android 9 - DOES NOT HAPPEN :x:
- Mi 10, Android 12 - DOES NOT HAPPEN :x:
- Samsung A32, Android 13 - IT HAPPENS :heavy_check_mark:

Some of my tests: https://www.minds.com/bashytest31/

### App version

4.34

### What is the current *bug* behavior?

images are being stretched horizontally

### What is the expected *correct* behavior?

images upload properly

### 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
Fatal error when replying to nested comments

### Summary

When replying to a nested reply, app throws fatal error.

### Steps to reproduce

- create test post
- write comment
- reply to the initial comment, continue hitting "reply" until eventually the app throws the error.
![XRecorder_04042023_053654](/uploads/50c172ce9c89e3271412daebadc382cd/XRecorder_04042023_053654.mp4)

### 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: 3.0
Store release - 4.34.0 - Android and iOS

<!---
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
--->
Store release - v4.34.0


## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->
Run a smoke test and review all already tested tasks from staging environment.

IAP: 
#4864
#4830
#4831
#4833
#4834
#4835

#4759
#4823
#4796
#4870
#4783
#4797
#4721
#4863
#4825
#4826
#4858
#4821
#4849
#4848
#4596 

#4838
#4812
#4840
#4857
#4656
#4804


## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->
- store release for Android and iOS

## UX/Design

<!---
Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged.
--->

## Mobile

<!---
Does a mobile card need to be created? Any notes for mobile?
--->

- [ ] Is Mobile Required?

## 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: 1.0