chore: dependency updates 20201203 #4648
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/invertase/react-native-firebase/qs1abud2i |
Codecov Report
@@ Coverage Diff @@
## master #4648 +/- ##
=======================================
Coverage 88.93% 88.93%
=======================================
Files 109 109
Lines 3712 3712
Branches 347 347
=======================================
Hits 3301 3301
Misses 369 369
Partials 42 42 |
mikehardy
force-pushed
the
dependency-updates
branch
from
fd66684 to
d4ddbc2
Compare
More test fixture differentiation is necessary for the test-reuse case, because even though the emulator data is wiped, the app has it's own firebase persistence and we are not cleaning that up, so future runs get more and more data unless either the test app is uninstalled/reinstalled or you just use deterministically separate fixtures like this commit
pre-compiled firestore sometimes gives me leveldb symbol collisions on linking in my local environment. It may be possible to integrate it in most cases but in some cases it fails, so de-integrating it for now
they were failing in local testing for some reason
on slower android devices this is necessary to avoid false-negative test results
mikehardy
force-pushed
the
dependency-updates
branch
from
d4ddbc2 to
58f9a2e
Compare
mikehardy
changed the title
hmhm2292
pushed a commit
to hmhm2292/react-native-firebase
that referenced
this pull request
Jul 13, 2021
…#4648) * feat(app, android): android bill of materials 26.1.1 + android dependencies * chore(test): regenerate Podfile.lock result of `yarn tests:ios:pod:install` * feat(app, ios): bump firebase-ios-sdk to 7.2.0 * fix(admob, ci): workaround admob test device detection issues * test(firestore, ci): +data fixture separation / +more tests More test fixture differentiation is necessary for the test-reuse case, because even though the emulator data is wiped, the app has it's own firebase persistence and we are not cleaning that up, so future runs get more and more data unless either the test app is uninstalled/reinstalled or you just use deterministically separate fixtures like this commit * test(messaging): fix test reuse case w/auto-init reset * test(e2e): update podfile, de-integrate pre-compiled firestore pre-compiled firestore sometimes gives me leveldb symbol collisions on linking in my local environment. It may be possible to integrate it in most cases but in some cases it fails, so de-integrating it for now * test(database, e2e): disable some flaky database tests * test(admob, e2e): disable rewarded ad loads on ios they were failing in local testing for some reason * test(firestore, e2e): add timeout to query snapshot callback test * test(auth, e2e): let sign-ins rest before testing callbacks on slower android devices this is necessary to avoid false-negative test results
androidIsForVivek
pushed a commit
to androidIsForVivek/react-native-firebase
that referenced
this pull request
Aug 9, 2021
…#4648) * feat(app, android): android bill of materials 26.1.1 + android dependencies * chore(test): regenerate Podfile.lock result of `yarn tests:ios:pod:install` * feat(app, ios): bump firebase-ios-sdk to 7.2.0 * fix(admob, ci): workaround admob test device detection issues * test(firestore, ci): +data fixture separation / +more tests More test fixture differentiation is necessary for the test-reuse case, because even though the emulator data is wiped, the app has it's own firebase persistence and we are not cleaning that up, so future runs get more and more data unless either the test app is uninstalled/reinstalled or you just use deterministically separate fixtures like this commit * test(messaging): fix test reuse case w/auto-init reset * test(e2e): update podfile, de-integrate pre-compiled firestore pre-compiled firestore sometimes gives me leveldb symbol collisions on linking in my local environment. It may be possible to integrate it in most cases but in some cases it fails, so de-integrating it for now * test(database, e2e): disable some flaky database tests * test(admob, e2e): disable rewarded ad loads on ios they were failing in local testing for some reason * test(firestore, e2e): add timeout to query snapshot callback test * test(auth, e2e): let sign-ins rest before testing callbacks on slower android devices this is necessary to avoid false-negative test results
androidIsForVivek
pushed a commit
to androidIsForVivek/react-native-firebase
that referenced
this pull request
Aug 9, 2021
…#4648) * feat(app, android): android bill of materials 26.1.1 + android dependencies * chore(test): regenerate Podfile.lock result of `yarn tests:ios:pod:install` * feat(app, ios): bump firebase-ios-sdk to 7.2.0 * fix(admob, ci): workaround admob test device detection issues * test(firestore, ci): +data fixture separation / +more tests More test fixture differentiation is necessary for the test-reuse case, because even though the emulator data is wiped, the app has it's own firebase persistence and we are not cleaning that up, so future runs get more and more data unless either the test app is uninstalled/reinstalled or you just use deterministically separate fixtures like this commit * test(messaging): fix test reuse case w/auto-init reset * test(e2e): update podfile, de-integrate pre-compiled firestore pre-compiled firestore sometimes gives me leveldb symbol collisions on linking in my local environment. It may be possible to integrate it in most cases but in some cases it fails, so de-integrating it for now * test(database, e2e): disable some flaky database tests * test(admob, e2e): disable rewarded ad loads on ios they were failing in local testing for some reason * test(firestore, e2e): add timeout to query snapshot callback test * test(auth, e2e): let sign-ins rest before testing callbacks on slower android devices this is necessary to avoid false-negative test results
androidIsForVivek
pushed a commit
to androidIsForVivek/react-native-firebase
that referenced
this pull request
Sep 15, 2021
…#4648) * feat(app, android): android bill of materials 26.1.1 + android dependencies * chore(test): regenerate Podfile.lock result of `yarn tests:ios:pod:install` * feat(app, ios): bump firebase-ios-sdk to 7.2.0 * fix(admob, ci): workaround admob test device detection issues * test(firestore, ci): +data fixture separation / +more tests More test fixture differentiation is necessary for the test-reuse case, because even though the emulator data is wiped, the app has it's own firebase persistence and we are not cleaning that up, so future runs get more and more data unless either the test app is uninstalled/reinstalled or you just use deterministically separate fixtures like this commit * test(messaging): fix test reuse case w/auto-init reset * test(e2e): update podfile, de-integrate pre-compiled firestore pre-compiled firestore sometimes gives me leveldb symbol collisions on linking in my local environment. It may be possible to integrate it in most cases but in some cases it fails, so de-integrating it for now * test(database, e2e): disable some flaky database tests * test(admob, e2e): disable rewarded ad loads on ios they were failing in local testing for some reason * test(firestore, e2e): add timeout to query snapshot callback test * test(auth, e2e): let sign-ins rest before testing callbacks on slower android devices this is necessary to avoid false-negative test results
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bumping test app dependencies to current while troubleshooting a build issue