giseldo/neodataset huggingface dataset:
Use user's supermind minimum limits on the composer



## Goal

Use the cash & tokens minimums from the user's settings to validate the supermind values on the composer

## What needs to be done

- [ ] Validate the minimums using the user's settings

## QA

- The minimum values should be the ones that the target user saved in the settings

## UX/Design

-

## Personas

- 


## Experiments

none

## Acceptance Criteria

- [ ] The minimum values should be the ones that the target user saved in the settings

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 2.0
Mobile app does not load more than 15 notifications

<!---
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

Mobile app does not load more than 15 notifications

### Steps to reproduce

1. Go to notifications
2. Scroll down
3. Notice that no more than 15 notifications load

### Platform information 

iPhone

### What is the current *bug* behavior?

No more than 15 notifications load at once

### What is the expected *correct* behavior?

If there is more than 15 notifications, it should be possible to load them.

### 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
Implement "See latest posts" feature on Supermind console

## Goal

Enable a creator to stay on the Supermind console and accept incoming offers as they arrive.

## What needs to be done

Implement the "See latest posts" feature from the Newsfeed, in the Supermind console.

Priority is the Inbound tab.

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

Implement the same component we have on the Newsfeed.

Change the language to read:

> See [n] latest offers

![image](/uploads/6b2710224c9865475cee8a4cbcf97eab/image.png)

## 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

- [ ] Given a creator is viewing the Supermind console > Inbound tab, when a new Supermind offer is received, then the "See latest offers" alert appears.
- [ ] Given the "See latest offers" alert appears, when the user clicks it, then the Supermind console is refreshed to display the new offers.

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 2.0
Create global Superminds feeds

<!---
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

(1) Easily audit live Superminds activity on the site
(2) Elevate Superminds activity and make it more discoverable

## What needs to be done

Create a global Superminds feed that collects all Superminds posts.

Add as a new tab to Discovery.

Use a mock for API retrieval of the feed until the backend is ready.

## 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
--->

- [ ] A new tab added to Discovery for "Superminds."
- [ ] The new tab displays a feed of all Superminds posts (offers and replies).
- [ ] Add a feature flag

## Definition of Ready Checklist

- [x] Definition Of Done (DoD)
- [x] Acceptance criteria
- [x] Weighted
- [x] QA
- [x] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 3.0
Supermind console single entity view

## Goal

Develop a simple UI for viewing + accepting/rejecting single supermind requests, originating from notifications (push, email, in-app).

## 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

- [Clickable Prototype](https://www.figma.com/file/EkJej3mKP2lSzmWTLoqlXD/Minds-Design-System?node-id=2494%3A15827)
- [Individual screens](https://www.figma.com/file/thrGepQAxmcMGB7MoEEckM/Supermind?node-id=2019%3A22498)


## 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

- [ ] Single supermind requests are linked to from notifications
- [ ] The entity is displayed within a modal that slides up.
- [ ] The modal is accessible within the newsfeed and notification notification stacks. 

- [ ] ...

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 0.0
When the comment input is shown it is causing a screen refresh



### Summary

When you try to comment on a post inside a group the screen is refreshed, removing the comments list component.

### Steps to reproduce
case 1
- Open a group
- Tap on the comment button of a post (without comments)
- The screen is refreshed and the comments list is removed from the screen

case 2
- Open a group
- Tap on the comment button of a post (with comments)
- Tap on add comment
- The screen is refreshed and the comments list is removed from the screen

### Platform information 

Android

### What is the current *bug* behavior?

The screen is refreshed and the user is unable to comment

### What is the expected *correct* behavior?

The input should be shown

### Relevant logs and/or screenshots
-

### Possible fixes

TBD

Story points: 2.0
Poor feed performance due to animated counters



### Summary

Poor feed performance due to animated counters

Discovered on #4473 (Reported by Mark)

### Steps to reproduce

Scroll on the feed

### Platform information 

both

### What is the current *bug* behavior?

a lot of stuttering on the feed

### What is the expected *correct* behavior?

It shouldn't affect the performance of the feed

### Relevant logs and/or screenshots

-

### Possible fixes

Disable animation on the feed for now

Story points: 2.0
Discovery scroll weirdness after refresh



### Summary

After scrolling and refreshing the discover screen using the tab button, the scroll starts to jump.

### Steps to reproduce

- open the discovery screen
- scroll many screens down
- refresh pressing the discovery tab button again
- scroll back

### Platform information

Both (reported on Android)

### App version

4.28

### What is the current *bug* behavior?

The scroll jumps

### What is the expected *correct* behavior?

The scroll should be smooth

### Relevant logs and/or screenshots

-

### Possible fixes

Maybe scrolling to top before refresh will solve this problem

Story points: 2.0
Comments: user is able to attach a link/rich-embed and a media at the same time

<!---
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

As Described in the title.

Reported by bashy

### Steps to reproduce

try to attach an image and add a link in the comments, you'll see that the rich embed and image appear overlapped.

- Begin composing a comment
- Add a link to the comment
- Add a piece of media (image or video) to the comment

### Platform information 

All

### What is the current *bug* behavior?

- The preview of the link is shown
- The preview of the media is shown
- The two previews overlap

### What is the expected *correct* behavior?

- The preview of the link is NOT shown
- The preview of the media IS shown

### 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.)

![image](/uploads/045877e36974066819b0acd1e72d05ec/image.png)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 2.0
Comments scroll error: scrollToIndex should be used in conjunction with getItemLayout

<!---
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

There seems to be an issue with focused comments scroll handling. 

Reported by Bill

### Steps to reproduce

TBD

### Platform information 

All

### What is the current *bug* behavior?

An error is thrown when deep navigating to a focused comment

### What is the expected *correct* behavior?

scrolling to focused comment should work as expected

### 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.)

![image](/uploads/24c912bc7229a547e32a8d139b677ff1/image.png)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 1.0
Fix typescript issue of Jest

<!---
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

Ever since we've added Jasmine to the project, the types for jest functions are broken. We need to fix this to avoid adding `@ts-nocheck` on top of our test files

### Steps to reproduce

try to use jest in a test file and you'll face typescript issues.

### Platform information 

All

### What is the current *bug* behavior?

jest types not recognized

### What is the expected *correct* behavior?

jest types are recognized

### 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
Superminds Cash Menu should appear for Channels with no bank account connected

### Summary

Cash menu appears for all Channels on mobile.

This works as expected on web. Needs to be consistent between mobile and web. 

### Steps to reproduce

1. Open minds web and login.
2. Navigate to a Channel with no bank account connected.
3. Tap on Superminds. 
4. Cash menu does not appear on Superminds popup.

### Platform information 

All

### What is the current *bug* behavior?

Cash menu does not appear for this channel

### What is the expected *correct* behavior?

Cash menu should appear for this channel

### Relevant logs and/or screenshots
![image](/uploads/691b9f45d6f60f6e28467d81ecaee7c9/image.png)

Story points: 3.0
Message in Chat option throws an error on Channel Page

### Summary

Error sending message shows up when sending messaging option via Channel page. 

### Steps to reproduce

1. Open app.
2. Navigate to Channel.
3. Subscribe to user.
4. Choose Message on Chat option. 

### Platform information 

iPhone 13 Pro

### What is the current *bug* behavior?

Throws an error.

### What is the expected *correct* behavior?

Should open chat app or ask to install chat app. 

![image](/uploads/9d4143978445b7e2bc8ce7351166ecb2/image.png)

Story points: 3.0
Supermind onboarding modal

## Goal

Communicate to users who are new to Superminds what Superminds are and why they should want to engage with them.

## What needs to be done

Implement 2x separate onboarding modals.

1. For users who are offering Superminds
2. For users who are replying to Superminds requests

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

- [Figma: Offering Superminds onboarding](https://www.figma.com/file/thrGepQAxmcMGB7MoEEckM/Supermind?node-id=545%3A14545)
- [Figma: Replying to Superminds onboarding](https://www.figma.com/file/thrGepQAxmcMGB7MoEEckM/Supermind?node-id=588%3A17217)

## Personas

Core users

## Experiments

n/a

## Acceptance Criteria

- [ ] Given a user has not yet engaged with Superminds as a sender, when the user first views the Superminds pricing panel in the composer, then the sender onboarding modal appears.
- [ ] Given a user has not yet engaged with Superminds as a receiver, when the user first navigates to the Superminds console inbound view, then the receiver onboarding modal appears.
- [ ] Given the user has previously viewed the sender modal, then it is not displayed again.
- [ ] Given the user has previously viewed the receiver modal, it it is not displayed again.
- [ ] Tap into dismissible widgets endpoint on engine

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 3.0
Multi Images: Gallery View

<!---
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
--->

This is part of the https://gitlab.com/minds/mobile-native/-/issues/4458.

Add a gallery view to multi image posts

https://www.figma.com/file/KlhBWJ05RhiYiYp66CiAb9/Multi-Image-Concept?node-id=75%3A3700

This gallery may be a good fit https://github.com/Flair-Dev/react-native-awesome-gallery

## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->

Add a gallery view to multi image posts

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->

look at https://gitlab.com/minds/mobile-native/-/issues/4458

## UX/Design

<!---
Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged.
--->

look at https://gitlab.com/minds/mobile-native/-/issues/4458

## Personas

<!---
Who does this user impact and why (optional)
--->

TBD

## Experiments

<!---
Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined.
--->

TBD

## Acceptance Criteria

<!--
Everyone should be able to understand what is expected to be delivered
--->

- [ ] It should support swiping between the images
- [ ] It should have the post actions bar
- [ ] Zooming

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 3.0
Migrate Tipsi Stripe to the official Stripe SDK



## Goal

Migrate to the official stripe SDK.

This will allow us to use google pay and this package is now the best option to use Stripe with RN

## What needs to be done

- [ ] Remove tipsi stripe
- [ ] Add the official SDK package
- [ ] Update the card selector and the stripe logic

## QA

All the stripe functionalities should be tested

## UX/Design

-

## Personas

-


## Experiments

-


## Acceptance Criteria

- [ ] Migrate to the official SDK
- [ ] The stripe functionality shouldn't be affected

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 3.0
Change CI release flow for Android


## Goal

With the new play store review process that may take a few days in some cases, we need to change the release flow on the CI

Currently, we are releasing the full version of the app on the web (custom auto-update) and after that submitting to the play store.

If we want a simultaneous release for iOS, play store, and web we need to send it to the stores first and await approval

I already changed the play store to manage the releases manually (Do not auto-release on approval)

## What needs to be done

- Move the play store to run before the web release
- Since the web release is generating the metadata, used by the play store release job, we need to replicate that into the play store

## QA
-


## UX/Design

-


## Personas

-


## Experiments

-


## Acceptance Criteria


- [ ] Create a generate metadata step
- [ ] The play store and the web release should be independent

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 2.0
Update react native to 0.69



## Goal

Update the react native framework



## What needs to be done

- Update react native to 0.69.x
- Additionally we can check if 0.70.0 works without issues


## QA

-


## UX/Design

-

## Personas

- 

## Experiments

-

## Acceptance Criteria

- [ ] The application must compile on both platforms
- [ ] The app should run without regressions

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 5.0
Changing tab doesn't load notifications



### Summary

Notifications are refreshing when changing tabs

### Steps to reproduce

Open notifications and change tabs

### Platform information 

Both

### What is the current *bug* behavior?

Notifications are refreshing when changing tabs

### What is the expected *correct* behavior?

It should refresh the list

### Relevant logs and/or screenshots

![imagen](/uploads/d2c7b695a22f8c62bd5ea6a0a71d1438/imagen.png)

### Possible fixes
TBD

Story points: 1.0
Counters showing 0



### Summary

The action counters (comments, votes, etc) are showing the 0 value.

### Steps to reproduce

Check the newsfeed

### Platform information 

both

### What is the current *bug* behavior?

Showing 0

### What is the expected *correct* behavior?

If the count is 0 it should not show the number

### Relevant logs and/or screenshots

![Screen_Shot_2022-09-06_at_11.51.00](/uploads/c820eb81992700f1fed0919b05dfd30d/Screen_Shot_2022-09-06_at_11.51.00.png)

### Possible fixes

Hide the component when the count is 0, but it may affect the animation between 0 and 1

Story points: 1.0
Support for multi-image uploads in composer

<!---
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

Enable Minds users to create activity posts that contain multiple images

* [Prototype](https://www.figma.com/proto/KlhBWJ05RhiYiYp66CiAb9/Multi-Image-Concept?page-id=72%3A1083&node-id=72%3A1084&viewport=-2896%2C881%2C1&scaling=scale-down&starting-point-node-id=72%3A1084&show-proto-sidebar=1)

## What needs to be done

* Update composer to support uploading up to 4x images only.
* Update activity post to display the new image matrix.
* Make some refactors to the full screen swiper (TBC)

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

* [Activity posts](https://www.figma.com/file/KlhBWJ05RhiYiYp66CiAb9/Multi-Image-Concept?node-id=223%3A2046)
* [Composer](https://www.figma.com/file/KlhBWJ05RhiYiYp66CiAb9/Multi-Image-Concept?node-id=114%3A2928)
* [Swiper](https://www.figma.com/file/KlhBWJ05RhiYiYp66CiAb9/Multi-Image-Concept?node-id=75%3A2179)

## Personas

Core Minds user

## Experiments

n/a

## Acceptance Criteria

- [ ] The composer enables a user to attach up to 4x images to an activity post before posting
- [ ] The images appear and are uploaded in the order in which they were added to the composer

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 3.0
Support for displaying multi-image activity posts

## Goal

Enable Minds users to create activity posts that contain multiple images.

## What needs to be done

Add support for displaying activity posts with multiple images. Activity posts can have up to 4x images. Images are cropped into uniform pieces of a grid. The count of images determines the grid layout.

Tapping an image in this grid opens the image in a modal that enables the user to view the full image [and swipe from one image to the next ?].

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design
https://www.figma.com/file/KlhBWJ05RhiYiYp66CiAb9/Multi-Image-Concept?node-id=72%3A1083

## Personas

Core Minds users.

## Experiments

n/a

## Acceptance Criteria

- [ ] Activity posts with multiple images appear in the app with all images presented in cropped grid format
- [ ] Tapping a cropped image in this grid displays the full image

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 3.0
iOS CI build is broken

### Summary

The iOS build is broken on the CI

https://gitlab.com/minds/mobile-native/-/jobs/2973464240

### Log

```
bash: line 1: syntax error near unexpected token `<'
bash: line 1: `<html><body>You are being <a href="https://gitlab.com/gitlab-org/incubation-engineering/mobile-devops/load-secure-files/-/raw/main/installer">redirected</a>.</body></html>'
```

Story points: 2.0