Device Information for React Native iOS and Android
MIT License
Bot releases are visible (Hide)
Published by mikehardy about 5 years ago
Published by mikehardy about 5 years ago
Published by Johan-dutoit about 5 years ago
Converted the project to TypeScript (A more in-depth discussion can be found here: https://github.com/react-native-community/react-native-device-info/pull/799)
Unknown
to unknown
for consistency f449ae7https://github.com/react-native-community/react-native-device-info/compare/v3.1.4...v4.0.1-beta.1
Published by mikehardy about 5 years ago
Thanks @tvanlaerhoven for reporting it!
https://github.com/react-native-community/react-native-device-info/compare/v3.1.3...v3.1.4
Published by mikehardy about 5 years ago
https://github.com/react-native-community/react-native-device-info/compare/v3.1.2...v3.1.3
Published by mikehardy about 5 years ago
https://github.com/react-native-community/react-native-device-info/compare/v3.1.1...v3.1.2
Published by mikehardy about 5 years ago
This release only has one functional change, and it's to bring the Windows version into the V3 world.
I don't have a react-native-windows development environment, so it was broken completely and I really appreciate @acoates-ms taking the time to shape it up. Thanks!
https://github.com/react-native-community/react-native-device-info/compare/v3.1.0...v3.1.1
https://github.com/react-native-community/react-native-device-info/compare/v3.0.1...v3.1.0
Published by mikehardy about 5 years ago
Thanks to @hufkens for PR #781 fixing tvOS
Otherwise unchanged from v3.0.0
Published by mikehardy about 5 years ago
You will need to adjust your code to use it. However, I believe all existing usage patterns should be supported.
Please see the upgrade guide here for information on breaking changes:
https://github.com/react-native-community/react-native-device-info/wiki/V2-to-V3-Migration-Guide
[Update - @acoates-ms fixed up the windows module and the result is released as 3.1.1 - windows users owe him some thanks!]
Original text from v3.0.0 release:
It is very likely that the windows port is broken right now. No windows users helped test it so it may not even compile. If this is important to you, you will have to file PRs to help maintain it as none of the current maintainers has a react-native-windows environment.
Each BREAKING CHANGE contains the required information to migrate. The example App.js shows sample usage.
getBuildNumber
returns string like iOS (https://github.com/react-native-community/react-native-device-info/pull/648)yarn add https://github.com/mikehardy/react-native-localize.git#e062f0d2dc3171dc18fdb7b7139d347ad03933dc
to maintain isAutoTimeZone + isAutoDateAndTime until mergedgetUsedMemory
(https://github.com/rebeccahughes/react-native-device-info/pull/356)Published by mikehardy about 5 years ago
This is tagged as @next
on npmjs so you may try it by using that tag.
Please refer to the CHANGELOG for all breaking change annotations to migrate.
https://github.com/react-native-community/react-native-device-info/blob/v3/CHANGELOG.md
https://github.com/react-native-community/react-native-device-info/compare/v3.0.0-rc.4...v3.0.0-rc.5
Published by mikehardy about 5 years ago
This is tagged as @next
on npmjs so you may try it by using that tag.
Please refer to the CHANGELOG for all breaking change annotations to migrate.
https://github.com/react-native-community/react-native-device-info/blob/v3/CHANGELOG.md
https://github.com/react-native-community/react-native-device-info/compare/v3.0.0-rc.3...v3.0.0-rc.4
Published by mikehardy about 5 years ago
This is tagged as @next
on npmjs so you may try it by using that tag.
Please refer to the CHANGELOG for all breaking change annotations to migrate.
https://github.com/react-native-community/react-native-device-info/blob/v3/CHANGELOG.md
https://github.com/react-native-community/react-native-device-info/compare/v3.0.0-rc.2...v3.0.0-rc.3
Published by mikehardy about 5 years ago
This is tagged as @next
on npmjs so you may try it by using that tag.
Please refer to the CHANGELOG for all breaking change annotations to migrate.
https://github.com/react-native-community/react-native-device-info/blob/v3/CHANGELOG.md
https://github.com/react-native-community/react-native-device-info/compare/v3.0.0-rc.1...v3.0.0-rc.2
Published by mikehardy about 5 years ago
This is tagged as @next
on npmjs so you may try it by using that tag.
Please refer to the CHANGELOG for all breaking change annotations to migrate.
https://github.com/react-native-community/react-native-device-info/blob/v3/CHANGELOG.md
Published by mikehardy about 5 years ago
This is tagged as @next
on npmjs so you may try it by using that tag.
Please refer to the CHANGELOG for all breaking change annotations to migrate.
https://github.com/react-native-community/react-native-device-info/blob/v3/CHANGELOG.md
Published by mikehardy about 5 years ago
This is tagged as @next
on npmjs.com so you may use that tag on npm/yarn install to test this.
This release fixes all the discrepancies between v2 and v3 that were detected on emulators. After checking real android/iOS devices this will go release candidate.
Read the v3.0.0-beta.1 release notes or the changelog for description of breaking changes so you can migrate.
Published by mikehardy about 5 years ago
This is tagged as @next
on npmjs.com so you can test it by trying that tag: npm i react-native-device-info@next
@ReactModule
annotation and NAME
constant a3cff96getUniqueID()
can be different in app extensions 60e75fahttps://github.com/react-native-community/react-native-device-info/compare/v2.3.2...v3.0.0-beta.1
Published by mikehardy about 5 years ago
The default stance of this module on android has moved to loading the constants asynchronously on android, a continuation of the work from #680 and #697 - these changes have been in place for quite some time now with zero reports of problems so this should be a minor change. The documentation has bee updated with information on how to disable it if it is a problem for you, but we expect this to be smooth and a performance enhancement for everyone.
Cheers
https://github.com/react-native-community/react-native-device-info/compare/v2.3.1...v2.3.2
Published by mikehardy about 5 years ago
npm audit fix
) bb5bd43https://github.com/react-native-community/react-native-device-info/compare/v2.3.0...v2.3.1