giseldo/neodataset huggingface dataset:
Email deep link for showing stripe restricted notice

<!---
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 email deep link for stripe restricted campaign is not working correctly.

### Steps to reproduce

Follow the [link](https://email.minds.com/wallet/cash/settings?__e_ct_guid=100000000000000063&campaign=when&topic=channel_improvement_tips&state=new&utm_medium=email&utm_campaign=stripe_is_restricted&utm_source=manual&utm_content=cta) which should open the Wallet screen with correct bank account settings. 

### Platform information 

Android

### What is the current *bug* behavior?


When following the [link](https://email.minds.com/wallet/cash/settings?__e_ct_guid=100000000000000063&campaign=when&topic=channel_improvement_tips&state=new&utm_medium=email&utm_campaign=stripe_is_restricted&utm_source=manual&utm_content=cta), it will open the Wallet screen with incorrect bank account settings. 

### What is the expected *correct* behavior?

When following the [link](https://email.minds.com/wallet/cash/settings?__e_ct_guid=100000000000000063&campaign=when&topic=channel_improvement_tips&state=new&utm_medium=email&utm_campaign=stripe_is_restricted&utm_source=manual&utm_content=cta), it will open the Wallet screen with correct bank account settings. 

### Relevant logs and/or screenshots

wrong:
![image](/uploads/24d5a24cb9b69aee23a0650855f4f727/image.png)

right:
![image](/uploads/2af06b495d1eb0384e71e5d8e7f36d42/image.png)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 3.0
Create UI entry point for in-app user verification

<!---
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

Create the UI entry point in the home screen for in-app user verification.

## What needs to be done

- create a widget in the in-app user verification module, which will be displayed in the home screen between the ,, and the news feed, as per [UI design](https://www.figma.com/file/buCViQPMNyQUNCdtDYUTbL/In-App-User-Verification?node-id=308%3A1321&t=I7n8h64U4ZiemLJt-0)
- create a screen in the in-app user verification module, to navigate from the widget as per the U design
- link the in-app verification process initiation with the continue button of the above screen

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

https://www.figma.com/file/buCViQPMNyQUNCdtDYUTbL/In-App-User-Verification?node-id=314%3A1541&t=I7n8h64U4ZiemLJt-0

## Personas

Developers

## 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

AC1:
- [ ] GIVEN that I am an unverified user
- [ ] WHEN I navigate to home screen
- [ ] THEN I will see a widget prompting for in-app verification 

AC2:
- [ ] GIVEN that I am a verified user
- [ ] WHEN I navigate to home screen
- [ ] THEN I will not see the widget prompting for in-app verification 

AC3:
- [ ] GIVEN that I am an unverified user
- [ ] AND I navigate to home screen 
- [ ] AND I see the widget prompting for in-app verification 
- [ ] WHEN I press on the Verify button
- [ ] THEN I will navigate to the Verify Channel screen 

AC4:
- [ ] GIVEN that I am an unverified user
- [ ] AND I an in the Verify Channel screen
- [ ] AND the `I agree to Terms` checkbox is off
- [ ] THEN the `Continue` button on the top-right is disabled

AC5:
- [ ] GIVEN that I am an unverified user
- [ ] AND I an in the Verify Channel screen
- [ ] WHEN I check the `I agree to Terms` checkbox (on)
- [ ] THEN the `Continue` button on the top-right will be enabled

AC6:
- [ ] GIVEN that I am an unverified user
- [ ] AND I an in the Verify Channel screen
- [ ] AND the `I agree to Terms` checkbox is no
- [ ] WHEN I press the `Continue` button on the top-right 
- [ ] THEN I navigate to the in-app verification initiation process screen


## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 3.0
Onboarding API called 12 times

<!---
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

Onboarding API is called 12 times in a single scenario.

### Steps to reproduce

1. Go on Discovery screen
2. Tap on a given post
3. Tap back icon on the top left or press android back button

### Platform information 

Both

### What is the current *bug* behavior?

In Discovery on back and forth displaying a post, the onboarding api is called 12 times.

### What is the expected *correct* behavior?

The api should not be called.

### 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
Relogin not working properly



### Summary

The relogin screen is not working

### Steps to reproduce

Once the tokens are expired type the password and press login

### Platform information 

both

### What is the current *bug* behavior?

The re-login screen doesn't go away

### What is the expected *correct* behavior?

It should re-login and navigate back to the previous screen

### Relevant logs and/or screenshots

-

### Possible fixes

TBD

Story points: 3.0
Re-Login not working 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

(Summarize the bug encountered concisely)

### Steps to reproduce

try to login back once the auth token expired.

### Platform information 

Android, possible iOS

### What is the current *bug* behavior?

When re-login, the bottom sheet modal is popping up again.

### What is the expected *correct* behavior?

When re-login, the modal should stay hidden.

### Relevant logs and/or screenshots

![video_2022-12-02_10-18-38](/uploads/a78343c2a0057081d09a1ec3ee47c37f/video_2022-12-02_10-18-38.mp4)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 3.0
Clicking on Group name returns error

<!---
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

Title

### Steps to reproduce

click the group name above any post (post has to belong to a group, obviously)

### Platform information 

android 11, mobile app 4.30.0

also apple xr, 4.30.1

### What is the current *bug* behavior?

![317611863_670706717841659_7190058193741129045_n](/uploads/d8f2b90c4ca01be536f3bc05a5eb8d59/317611863_670706717841659_7190058193741129045_n.jpg)

### What is the expected *correct* behavior?

user should be redirected to the group

### 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
Chores: Remove warnings, logs and other small tasks

<!---
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

Clean-up the code for warnings, logs and other chores.

## What needs to be done

- remove warnings
- remove console.log 
- remove API calls to client3.google.com
- 

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

<!---
Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged.
--->


## Personas

<!---
Who does this user impact and why (optional)
--->


## Experiments

<!---
Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined.
--->


## Acceptance Criteria

<!--
Everyone should be able to understand what is expected to be delivered
--->

- [ ] ...

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Chores

Story points: 3.0
Spinner always on on newsfeed list with only one post

<!---
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 only one post in the main feed, the spinner is always on at the bottom of the feed.

### Steps to reproduce

Login with appledemo account which has only one post in the main feed

### Platform information 

Both

### What is the current *bug* behavior?

When scrolling down, the spinner show loading but do not hide after no more items.

### What is the expected *correct* behavior?

When scrolling down, the spinner should hide after scrolling down and no more items.


### Relevant logs and/or screenshots

(Paste any relevant logs - please use code blocks (```) to format console output,
logs, and code as it's very hard to read otherwise.)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 2.0
Chore: Create OpenApi files for current API calls

<!---
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

To clearly document and maintain API documentation and build the foundation for contract-based development.

## What needs to be done

- create stoplight entries for API calls (home, discovery, notifications, profile)
- create a openApi folder in the app's repo
- create an inventory of existing API calls in the app
- create openAPI files for API calls
- collate related API calls in the same openAPI file where appropriate

## 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

Developers

## 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: 8.0
Implement defaults for Label, Switch, Progress and Slider

<!---
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

Implement defaults for Label, Switch, Progress and Slider

## What needs to be done

- Implement defaults for Label
- Implement defaults for Switch
- Implement defaults for RadioButton/Group
- Implement defaults for Progress
- Implement defaults for Slider


## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

- [Minds design system](https://www.figma.com/file/EkJej3mKP2lSzmWTLoqlXD/Minds-Design-System?node-id=59%3A2&t=y87OMAD6MnCx98qa-0)

## 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: 8.0
Implement defaults for TextInput

<!---
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

Implement defaults for TextInput


## What needs to be done

Implement defaults for TextInput

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

- [Minds design system](https://www.figma.com/file/EkJej3mKP2lSzmWTLoqlXD/Minds-Design-System?node-id=59%3A2&t=y87OMAD6MnCx98qa-0)


## Personas

Developers

## 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: 5.0
Implement defaults for Avatar

<!---
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

Implement defaults for Avatar

## What needs to be done

Implement defaults for Avatar

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

- [Minds design system](https://www.figma.com/file/EkJej3mKP2lSzmWTLoqlXD/Minds-Design-System?node-id=59%3A2&t=y87OMAD6MnCx98qa-0)

## Personas

Developers

## 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
Implement defaults for LineItem

<!---
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

Implement defaults for LineItem

## What needs to be done

- create defaults for LineItem
- add support for avatar in icon's place

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

- [Minds design system](https://www.figma.com/file/EkJej3mKP2lSzmWTLoqlXD/Minds-Design-System?node-id=59%3A2&t=y87OMAD6MnCx98qa-0)

## 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: 5.0
Implement default top tab bar

<!---
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

Implement default top tab bar

## What needs to be done

- implements tab bar component with theme support
- check for horizontal scroll


## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

- [Minds design system](https://www.figma.com/file/EkJej3mKP2lSzmWTLoqlXD/Minds-Design-System?node-id=59%3A2&t=y87OMAD6MnCx98qa-0)

## Personas

Developers

## 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
Implement default icon button with labels

<!---
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

Implement default icon button with labels


## What needs to be done

- create component for icon button
- add optional support for label below
- add selected and press status


## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

- [Minds design system](https://www.figma.com/file/EkJej3mKP2lSzmWTLoqlXD/Minds-Design-System?node-id=59%3A2&t=y87OMAD6MnCx98qa-0)

## Personas

Developers


## 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
Implement current icons using SVG

<!---
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

Implement current icons using SVG

## What needs to be done

- get the list of icons from the app in figma
- export them as SVG and add them to the app
- add support for SVG import in babel config
- hook Tamagui to use SVG icons


## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

- [Minds design system](https://www.figma.com/file/EkJej3mKP2lSzmWTLoqlXD/Minds-Design-System?node-id=59%3A2&t=y87OMAD6MnCx98qa-0)

## Personas

Developers

## 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: 8.0
Implement buttons with all variants on all dimensions and defaults

<!---
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

Implement buttons with all variants on all dimensions and defaults

## What needs to be done

- define defaults and variants in Tamagui config for buttons
- implement all variants as per design system.

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

- [Minds design system](https://www.figma.com/file/EkJej3mKP2lSzmWTLoqlXD/Minds-Design-System?node-id=59%3A2&t=y87OMAD6MnCx98qa-0)
- [Progress Design](https://www.figma.com/file/CZByU9CQwVKCI24EaMuf78/Design-system-playground?node-id=273%3A29043&t=a5ShlcTe2bE3q97Z-0)

## Personas

Develpers

## 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: 5.0