giseldo/neodataset huggingface dataset:
Video playing in background bug

* View and play a video within the full screen mode.
* Navigate to the channel, by tapping the channel banner.
* Note how the video audio continues to play in the background.

<details><summary>Click to see screencast</summary>
![RecordIt-1652794486](/uploads/e28dd19bec0be32e4425233b8e105c52/RecordIt-1652794486.mov)
</details>

Story points: 3.0
Send to option is not detecting the chat installed



### Summary

When tapping send to it is not detecting the chat app and opening the store

### Steps to reproduce

On an Android device with the chat and minds app installed
- open the app
- Tap on the Share button of a post
- Tap `send to`

### Platform information 

Android

### What is the current *bug* behavior?

Opens the minds chat app in the store 

### What is the expected *correct* behavior?

It should share with the chat app

### Relevant logs and/or screenshots

![imagen](/uploads/0dd7781a71bc6ac0416d9b533ff4d587/imagen.png)

### Possible fixes

Check chat install detection

Story points: 2.0
Deep linking not working on Android 12


### Summary

HTTPS deep links are not working on Android 12

A new endpoint was added to enable deep-links but the AndroidManifest also needs changes

engine#2318

### Steps to reproduce

Press a deep link and it is opened on the browser

### Platform information 
Android

### What is the current *bug* behavior?

Open in browser

### What is the expected *correct* behavior?

Should ask to open in-app

### 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
Main newsfeed stuttering



### Summary

The newsfeed seems to have more stuttering than the previous stable version

### Steps to reproduce

Scroll the main newsfeed fast (Most noticeable on android)

### Platform information 

Both

### What is the current *bug* behavior?

Performance issues

### What is the expected *correct* behavior?

It should be at least as fast as the previous version

### Relevant logs and/or screenshots


### Possible fixes

We need to profile the app and check the changes changes

Story points: 2.0
Transparent space on channel's feed

<!---
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 scrolling the feed and going back a post seems to turn transparent and the banner can be seen

### Steps to reproduce

Open the channel screen and scroll the feed down and up

### Platform information 

Detected on Android for now

### What is the current *bug* behavior?

Transparent post

### What is the expected *correct* behavior?

The post should be rendered correctly

### Relevant logs and/or screenshots
![image](/uploads/d8a3e87b39deb3c647da9fb200922425/image.png)

### Possible fixes

It may be a regression caused by the latest changes of the SmartImage component or the reanimated update

Story points: 3.0
Social Compass component is not an observer



### Summary

The Social Compass component is not an observer, given that it uses the useApiFetch hook it should be.

Without that the component is not rendered when the useApiFetch information changes, just when the parent does it

### Steps to reproduce

It should be reproduced by debugging the code

### Platform information 

Both

### What is the current *bug* behavior?

Not reacting to fetch results or errors

### What is the expected *correct* behavior?

It should update when the fetch store observables change

### Relevant logs and/or screenshots

none

### Possible fixes

Make it observable

Story points: 1.0
Update react-native to 0.68.1


## Goal

Update react-native to 0.68 to take advantage of the improvements and fixes it provides.

This version includes an opt-in for the new architecture (Turbo modules and Fabric renderer) that improves the performance and init speed. But because our app has many dependencies and all of them should implement the new architecture we are not going to be able to use it yet.


## What needs to be done

- Update react-native
- Check if some packages need updating
- Test build/runtime on both platforms

## QA

General smoke testing

## UX/Design


## Personas

It is a maintenance task but it still may improve the performance/stability of the app for all the users

## Experiments

none


## Acceptance Criteria

- [ ] React native should be updated
- [ ] Build process should work locally and on the CI for both platforms
- [ ] App should run normally after the update

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Updat

Story points: 8.0
Play Store deployment fails with large changelogs


### Summary

The CI job to deploy the android app to the playstore is failing when the changelog is too long.

We need to truncate or make a resume of the changelog (500 chars max)

### Steps to reproduce

Changelog for the version longer than 500 chars

### Platform information 

Android, gitlab CI

### What is the current *bug* behavior?

Deploy fails

### What is the expected *correct* behavior?

It should deploy successfully 

### Relevant logs and/or screenshots

https://gitlab.com/minds/mobile-native/-/jobs/2328387572

### Possible fixes

Truncate or make a smaller public version of the changes

Story points: 1.0
Plan and define required changes for a more streamlined workflow


## Goal

Define the workflow and the required changes to provide a more streamlined development/release workflow for mobile.

 - Have an automatic build for the current dev branch for both platforms (Currently available for Android only)
 - Ideally, have one single development branch 
 - Ideally, move iOS CI to gitlab
 - Remove current detox e2e from circle CI
 - Add e2e to GitLab CI using the new implementation (Browserstack real devices)
 - It should include codepush patch release

## Acceptance Criteria

- [ ] Documented new workflow
- [ ] Create new tasks for required changes

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

## Created Tasks
 
https://gitlab.com/minds/mobile-native/-/issues/4309

Story points: 3.0
Uploads fail on iOS when the app is moved to the background



### Summary

The upload (requests) are canceled when the app is moved to the background (iOS)

### Steps to reproduce

- Open the composer
- attach a large media
- move the app to the background before it finishes the upload

### Platform information 

iOS

### What is the current *bug* behavior?

Network request failed

### What is the expected *correct* behavior?

It should continue the upload in the background

### Relevant logs and/or screenshots

![IMG_AD9BAA3BD269-1](/uploads/6b3fb097ce4665f2863b0b3c582ec614/IMG_AD9BAA3BD269-1.jpeg)

### Possible fixes

Vydia/react-native-background-upload can be useful

Story points: 3.0
App stack re-renders while switching user causing some hooks to be fired



### Summary
The main screen of the app (AppStack) is rendered a few times while switching users.

This causes some hooks for example to be fired with the old and new user sessions in a very close window.

In order to prevent some weird race conditions, we should disable the app stack while switching users

### Steps to reproduce

Switch users
- Social compass hook is called with both users

### Platform information 
Both

### What is the current *bug* behavior?
- App stack re-renders while switching users

### What is the expected *correct* behavior?

- App stack should render again when the switch finishes


### Possible fixes

make the AppStack return null while switching users

Story points: 1.0
Blurhash: Some posts don't get deblurred on 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

Some posts don't get deblurred on Android

### Steps to reproduce

- use android
- use the latest version (4.24.0)
- Make sure your latest feed contains an image post
- Notice that the blurhash of that image doesn't get removed
  - This issue may not necessarily have anything to do with the first post and other posts might be affected

### Platform information 

Android

### What is the current *bug* behavior?

I just described above

### What is the expected *correct* behavior?

Blurhash should only appear when the image hasn't been loaded yet. When the image loads it should get removed. And it shouldn't appear at all if the image was previously loaded.

### Relevant logs and/or screenshots

![blurhash-issue](/uploads/8a52202b7ca7d60553dc9f3b385419ee/blurhash-issue.mov)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 2.0
Updated react-native-fast-image fork



## Goal

Update our fork of the fast image to get the latest features/fixes 
It includes some fixes and updated versions of the graphic libraries for both platforms

## What needs to be done

 - Update the fast image fork with the latest changes
 - Test that our custom functionality is still working (get cache path)

## QA

Images should be displayed correctly

## UX/Design
None


## Personas

Improved stability for all the users

## Experiments

none

## Acceptance Criteria

- [ ] The custom functionality must not be affected

## Definition of Ready Checklist

- [x] Definition Of Done (DoD)
- [x] Acceptance criteria
- [ ] Weighted
- [x] QA
- [x] UX/Design
- [x] Personas
- [x] Experiments

Story points: 3.0
Limit camera video resolition to 1080p



## Goal

Improve the upload speed and the backend transcode time by limiting the resolution of the in-app video capture to 1080p

This feature was implemented already in the transcoding MR https://gitlab.com/minds/mobile-native/-/merge_requests/1740 that we will not use for the moment given that it increases the APK size by a 300% and in some devices the transcoding is too slow to provide an actual improvement.

## What needs to be done

Create a new MR only with the implementation for the camera resolution limitation https://gitlab.com/minds/mobile-native/-/merge_requests/1740

## QA



## UX/Design

None


## Personas

It will improve the UX when uploading videos recorded with the app given that the upload time will be reduced.

## Experiments

none


## Acceptance Criteria

- [ ] It should record videos with a resolution of 1080p
- [ ] It should select the better video resolution in case 1080p is not available on the device

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 2.0
Throw a better error message when video upload fails

### Summary

Currently, a network request error is displayed when internet goes down during uploading a video on Minds.

Reported via Testing Channel. 

### Steps to reproduce

1. Open minds app.
2. Go to composer.
3. Upload a video.
4. Make sure internet connectivity goes bad.

### Platform information 

iOS & Android

### What is the current *bug* behavior?

Throws network error.

### What is the expected *correct* behavior?

Should throw a better error message and ask user to try again with internet so it is clear. Wording to be confirmed with @michaelfbradley

Story points: 1.0
Unable to Filter content by Date Range

### Summary

When filtering content by date range, user is brought back to "All" as the filter option after inputting the date range and hitting "Done". Range is never accepted, therefore filter is never applied.

### Steps to reproduce

Log in --> filter --> select a valid date range (start and end dates are both in the past or present)

### Platform information 

iPhone and Android app

### What is the current *bug* behavior?

Date range filter is never applied, filter behavior reverts to "all". The radial button never moves.

### What is the expected *correct* behavior?

Radial button should move to the selected range, indicating a successful application of the filter.

### Relevant logs and/or screenshots

![iPhone_SetRange](/uploads/f72edd7874b82b2959e16a68360b33c2/iPhone_SetRange.mp4)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 2.0
Add codepush release creation steps on the CI


## Goal

Be able to do patch releases in a quick way using code push and only pressing a button on the CI

## What needs to be done

We need to create a new CI stage that will be available for the patch/x.y.z branches.

It should include
 - Spect tests
 - Manual job to deploy to code push `staging`
 - Manual job to deploy to code push `production`

## QA

It should be tested until the staging step.

- Create a patch/x.y.z branch with some changes
- Run the staging deploy on the CI
- Check on appcenter that the bundle is uploaded

Extra test for the entire flow (in-app update)

- Install the stanging version of the app (The latest Minds-release-x_y_z.apk)
- It should update silently and the changes should be visible after restarting the app

## UX/Design

-

## Personas

Developers: Improve our release flow
Users: receive update faster and silently

## Experiments

-


## Acceptance Criteria

- [ ] It should add the required steps to the CI
- [ ] It should do the bundle for each platform in a separate job and in parallel (In case one fail we can run it again)

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 2.0
Update report categories

<!---
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


The goal is to streamline the report modal by clarifying categories and removing duplicate and/or unused entries.

## What needs to be done

Report categories should be updated to reflect the chart in the following section. Below is a list of changes:

**Text-only changes**

1. Change 'pedophilia' to 'sexualization of minors'
2. Change 'Encourages or incites violence' to 'Incitement to violence'
3. Change 'Impersonates' to 'Impersonation'
4. Change 'Copyright' to 'Intellectual Property Violation'
5. Change 'Token manipulation' to 'Inauthentic engagement'
6. Change "Sex trafficking" to "Trafficking"

**Removals**

Remove the following categories:

1. Trademark infringement (because it is merged with IP violation)
2. Incorrect use of hashtags (because it does nothing)

**Modifications**

Under 'Intellectual Property Violations' (formerly 'Copyright') we need to link to the Zendesk DMCA form instead of saying to email to copyright@minds.com.

https://support.minds.com/hc/en-us/requests/new?ticket_form_id=360003221852

![image](/uploads/3468e4dcc934af01a792d1680dbaf7da/image.png)

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->

Minimal QA: make sure reporting under the new labels generates the correct report.

Check emails.

## 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
--->

This change impacts typical Minds users who make reports.

## Experiments

<!---
Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined.
--->

No experiments are needed.

## Acceptance Criteria

<!--
Everyone should be able to understand what is expected to be delivered
--->

- [ ] Labels are correctly changed for users on the report modal

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 2.0
[GAT] The user is taken back to the post selecting the "send tip" button having no wallet or no tokens

Steps to Reproduce:
1. Open the app as a logged user
2. Open a post
3. Select "tip" button
4. Select the "send tip" button having no wallet or no tokens
5. The user is taken back to the post

Actual Results
"The user is taken back to the post selecting the "send tip" button having no wallet or no tokens"

Expected Results
"An error about no tokens appears selecting the "send tip" button having no wallet or no tokens"

https://testers.testerwork.com/videos/07650807b71a4483e1a4af777b7cf44f7b386006fd3f14d05e3097ecc385dc353ab4ae317654fbd1ef0067e15bd55db9

Story points: 1.0
Update reanimated and the gesture handler


## Goal

Update the reanimated and gesture handler packages

...

## What needs to be done

Update gesture handler to v2 (compatible with v1)
Update reanimated

Additionally we should check if that helps also to fix the Moti issues #4024

...

## QA

We should check that the app runs smoothly and the gestures are working as expected.

The reanimated update may affect all the animations of the app, even the screen transitions
...

## UX/Design

None

...

## Personas

It may improve UI animations performance and the gesture handling

...

## Experiments

None

...

## Acceptance Criteria

- The application must works without changes after the update

## Definition of Ready Checklist

- [x] Definition Of Done (DoD)
- [x] Acceptance criteria
- [x] Weighted
- [x] QA
- [x] UX/Design
- [x] Personas
- [x] Experiments

Upd

Story points: 1.0
Replace rn-placeholder with Moti's skeleton


## Goal

Remove unnecessary dependency and improve the performance/smoothness of the loading placeholders of the app.

## What needs to be done

1. Replace the placeholders of `rn-placeholder` with the new Moti's skeleton (implemented with reanimated)

Components to be refactored:

- ChannelListItemPlaceholder
- DiscoveryTrendPlaceHolder
- ActivityPlaceHolder 
- NotificationPlaceHolder
- BarPlaceholder
- UpgradeScreenPlaceHolder

2. remove `rn-placeholder`


## QA

The placeholders should work in a similar fashion to the current ones

![Simulator_Screen_Shot_-_iPhone_13_-_2022-05-09_at_11.27.34](/uploads/b70ab74cb4d385379aea7fa49ec47ad3/Simulator_Screen_Shot_-_iPhone_13_-_2022-05-09_at_11.27.34.png)

## UX/Design

No designs necessary


## Personas

It will improve the smoothness of the loading placeholders animations, giving a better performance perception for all users


## Experiments

No experiments needed


## Acceptance Criteria

It should replace all the current components with a similar design (The animation may differ)

## Definition of Ready Checklist

- [x] Definition Of Done (DoD)
- [x] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [x] UX/Design
- [x] Personas
- [x] Experiments

Story points: 3.0
Text lost in composer screen (android)



### Summary

The text is lost when pressing the hardware back button in the camera screen

### Steps to reproduce

- Open composer
- Write some text
- Tap the camera button
- Press the hardware back button
- Text is lost

### Platform information 

Android

### What is the current *bug* behavior?

Text is lost

### What is the expected *correct* behavior?

It should keep the text (Like when you press the X close button)

### Possible fixes

Add a custom back button handler for the camera screen

Story points: 2.0
(Bug) Notifications not loading properly

<!---
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

Users report notifications not loading properly in new release of the minds app

Source (With video): https://www.minds.com/newsfeed/1361390102860795916

Story points: 3.0
Channel Recommendation See More Navigation Issue

<!---
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

See More Page navigates below the bottom sheet

### Steps to reproduce

on channel recommendation widget anywhere -> press see more -> press on a recommendation => navigation happens beneath the bottom sheet

### Platform information 

both

### What is the current *bug* behavior?

I just explained above

### What is the expected *correct* behavior?

navigation should happen on top of the bottom sheet.

### Relevant logs and/or screenshots

![Simulator_Screen_Recording_-_iPhone_13_-_2022-04-14_at_13.18.19](/uploads/0287902d2185ed7edaf83d92bb2a2463/Simulator_Screen_Recording_-_iPhone_13_-_2022-04-14_at_13.18.19.mov)

### Possible fixes

We fixed this in hashtags component by differentiating the navigation ∫ased on whether we're navigating with the `NavigationService` navigation. My proposed quick fix is to do the same thing with the ChannelListItem but Ideally, we want to manage this in a central place so issues like this won't happen again

Story points: 2.0
NSFW Posts disappear on iOS

### Summary

Now that we are filtering NSFW post, they look weird when they automatically disappear from the profile and newsfeed for the user who created the post. 

### Steps to reproduce:

1. Open minds app on iOS.
2. Login successfully. 
3. Navigate to profile or newsfeed.
4. Create a post.
5. Edit post and mark as NSFW.
6. Post disappears

### Platform information 

v4.23 - iOS

### What is the current *bug* behavior?

Post disappears

### What is the expected *correct* behavior?

To discuss - mostly post should stay with warning if it is your own post.

### What needs to be done?

Remove the option to create NSFW content.

### Relevant logs and/or screenshots

![PostDisappears](/uploads/9eaddc12894c048ea21942fa77039600/PostDisappears.mov)

Story points: 3.0
[GAT] Android - Nothing happens when selecting a GIF from keyboadd when writing a new post

Actual Results
"Nothing happens when selecting a GIF from keyboadd when writing a new post
"

Expected Results
"All buttons and options will show response while navigating the app"

https://testers.testerwork.com/videos/f63c050a9554212becb77e85d7855f5a1e2f8bcb6f8096db018a60037eac5fbd7288245144bf08ccfe375075359fe8a0

Story points: 3.0