The ListView component has been removed from the React Native and hence the project is giving an error during build. Attached below is the screenshot of the error.

**
EDIT: The issue has been fixed in version v0.8.0. Please update the dependencies to resolve the issue
**
Hi, @prabhjodhOYO .
Did you find any break-through ?
@KiranUppunda The issue has been fixed in version v0.8.0. Please update the dependencies to resolve the issue.
@prabhjodhOYO please tell me which dependencies to i need to update and the issue is fixed in version v0.8.0 of what i could not get it?
@prabhjodhOYO please tell me which dependencies to i need to update and the issue is fixed in version v0.8.0 of what i could not get it?
@DheereshSinghKarki Upgrade react-native-keyboard-aware-scroll-view to latest version
@prabhjodhOYO please tell me which dependencies to i need to update and the issue is fixed in version v0.8.0 of what i could not get it?
@DheereshSinghKarki Upgrade react-native-keyboard-aware-scroll-view to latest version
but i have not installed this package and neither did i used listview in any of my files
@prabhjodhOYO Sir i have not used this package or listview in my code

After installing the package it does not show in package.json file
I have already replaced this library, but every time I see a warning after npm install. Help only removing this in react-native-implementation.js:
Object.defineProperty(module.exports, 'ListView', {
configurable: true,
get() {
invariant(
false,
'ListView has been removed from React Native. ' +
'See https://fb.me/nolistview for more information or use ' +
'`deprecated-react-native-listview`.',
);
},
});
@prabhjodhOYO your solution solved my issues
@prabhjodhOYO please tell me which dependencies to i need to update and the issue is fixed in version v0.8.0 of what i could not get it?
@DheereshSinghKarki Upgrade react-native-keyboard-aware-scroll-view to latest version
but i have not installed this package and neither did i used listview in any of my files
Remove all the references to native-base. Do a quick search for the same in node_modules. That seems to be the work-around.
Most helpful comment
@KiranUppunda The issue has been fixed in version v0.8.0. Please update the dependencies to resolve the issue.