withIAPContext freeze my custom context
See original GitHub issuePlease use Discussion board if you want get some help out of it. Please report issue if there is a bug.
Version of react-native-iap
7.4.1
Version of react-native
0.64.2
Platforms you faced the error (IOS or Android or both?)
Both
Expected behavior
Update state of my Providers. I read data from local database and save on my context and the data does not update.
Actual behavior
Using withIAPContext
State data does not update
Tested environment (Emulator? Real Device?)
Emulator
Steps to reproduce the behavior
import React from "react";
import { Provider } from "react-redux";
import { MenuProvider } from 'react-native-popup-menu';
import { NativeBaseProvider } from 'native-base';
import { withIAPContext } from 'react-native-iap';
import AppNavigation from "./src/routes";
import store from "./src/utils/store";
import { TabProvider } from "./src/utils/TabProvider";
const Root = () => (
<Provider store={store}>
<NativeBaseProvider>
<TabProvider>
<MenuProvider>
<AppNavigation />
</MenuProvider>
</TabProvider>
</NativeBaseProvider>
</Provider>
)
export default withIAPContext(Root);
My app stuck on loading because the value on my custom context doesn’t update.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
dooboolab/react-native-iap (Raised $40.00) - Issuehunt
Add custom data to product purchase in global listener ... After eject my expo project, and link, Build fail ... withIAPContext freeze my...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hi @r0b0t3d. Sorry for delay.
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community’s attention? This issue may be closed if no further activity occurs. You may also label this issue as “For Discussion” or “Good first issue” and I will leave it open. Thank you for your contributions.