facebook/react-native 89094
A framework for building native apps with React.
luin/ioredis 7973
🚀 A robust, performance-focused and full-featured Redis client for Node.js.
react-native-community/react-native-webview 2869
React Native Cross-Platform WebView
react-native-community/cli 1356
React Native command line tools
react-native-community/react-native-netinfo 816
React Native Network Info API for Android & iOS
fullstackreact/react-native-firestack 725
A firestack v3 react-native implementation
invertase/denque 201
The fastest javascript implementation of a double-ended queue. Used by the official Redis, MongoDB, MariaDB & MySQL libraries for Node.js and many other libraries.
Babel preset for Node 6.x (ES6 / ES2015)
NodeRedis/node-redis-parser 70
A high performance Redis protocol (RESP) parser for JavaScript. Used by Node Redis & ioredis.
bderiso/Microsoft-Github-acquisition 31
Information & debate about the acquisition
issue commentinvertase/react-native-firebase
apple is rejecting apps for kids because of IDFA
Latest SDKs released today, so this should be fixed.
comment created time in a day
push eventinvertase/react-native-firebase
commit sha 4b8c97aab936ffa27d15d6b2476ea45ec4155cac
Update packages/firestore/lib/utils/index.js
push time in a day
Pull request review commentinvertase/react-native-firebase
feat(firestore): onSnapshotsInSync API
export function parseSnapshotArgs(args) { return { snapshotListenOptions, callback, onNext, onError }; }++export function parseSnapshotInSyncArgs(args) {+ if (args.length === 0) {+ throw new Error('expected at least one argument.');+ }++ // Ignore onComplete as its never used+ const NOOP = () => {};+ let callback = NOOP;+ let onError = NOOP;+ let onNext = NOOP;++ /**+ * .onSnapshot(Function...+ */+ if (isFunction(args[0])) {+ /**+ * .onSnapshot(() => {}, (error) => {}+ */+ if (isFunction(args[1])) {+ onNext = args[0];+ onError = args[1];+ } else {+ /**+ * .onSnapshot((snapshot, error) => {})+ */+ callback = args[0];+ }+ }++ /**+ * .onSnapshot({ complete: () => {}, error: (e) => {}, next: () => {} })+ */+ if (isObject(args[0]) && args[0].includeMetadataChanges === undefined) {+ if (args[0].error) {+ onError = args[0].error;+ }+ if (args[0].next) {+ onNext = args[0].next;+ }+ }++ if (!isFunction(onNext)) {+ throw new Error("'observer.next' or 'onNext' expected a function.");+ }++ if (!isFunction(onError)) {+ throw new Error("'observer.error' or 'onError' expected a function.");+ }++ return { callback, onNext, onError };+}
}
comment created time in a day
PR closed invertase/react-native-firebase
Investigation into https://github.com/invertase/react-native-firebase/issues/3719#event-3453380108
pr closed time in a day
pull request commentinvertase/react-native-firebase
bug(storage): deprecated storage paths investigation
Doesn't seem to be any changes required here anymore as they're all already on master.
comment created time in a day
Pull request review commentinvertase/react-native-firebase
tests(database): added test case for db value guarantee
describe('database().ref().once()', () => { callback.should.be.calledOnce(); callback.should.be.calledWith({ nuggets: 57 }); });++ it.only('guarantee to resolve after child_added', async () => {
it('guarantee to resolve after child_added', async () => {
comment created time in a day
push eventinvertase/react-native-firebase
commit sha 03fe17fada1ea7851d70898e7bdc0a249ea1c86c
docs(analytics): update `setAnalyticsCollectionEnabled` example (#4027) Co-authored-by: Mike Diarmid <[email protected]>
push time in a day
PR merged invertase/react-native-firebase
Description
<!-- Thanks for submitting a pull request! Please provide enough information so that others can review your pull request properly. --> <!-- Explain the motivation for making this change e.g. what existing problem does the pull request solve? -->
Related issues
<!-- If this PR fixes an issue, include "Fixes #issueNumber" to automatically close the issue when the PR is merged. -->
Release Summary
<!-- An optional description that you want to appear on the generated changelog -->
Checklist
- I read the Contributor Guide and followed the process outlined there for submitting PRs.
- [ ] Yes
- My change supports the following platforms;
- [ ]
Android - [ ]
iOS
- [ ]
- My change includes tests;
- [ ]
e2etests added or updated inpackages/\*\*/e2e - [ ]
jesttests added or updated inpackages/\*\*/__tests__
- [ ]
- [ ] I have updated TypeScript types that are affected by my change.
- This is a breaking change;
- [ ] Yes
- [ ] No
Test Plan
<!-- Demonstrate the code you've added is solid, e.g. test logs or screenshots. -->
Think react-native-firebase is great? Please consider supporting the project with any of the below:
- 👉 Star this repo on GitHub ⭐️
- 👉 Follow
React Native FirebaseandInvertaseon Twitter
pr closed time in a day
pull request commentinvertase/react-native-firebase
docs(analytics): update `setAnalyticsCollectionEnabled` example
Thank you :)
comment created time in a day
push eventgaodeng/react-native-firebase
commit sha 81d1d659ac8fd98977abb5358cff430295344d6a
Update index.md
push time in a day
delete branch invertase/react-native-firebase
delete branch : @dackers86/update-creation-time-on-emulator
delete time in a day
push eventinvertase/react-native-firebase
commit sha 07f98bd79800921445e90c6833753df8c963a694
tests(auth): added tests for checking creation time across multiple created users (#3776)
push time in a day
PR merged invertase/react-native-firebase
Investigation into creation times that are not updating when creating multiple users on an emulator. Please see https://github.com/invertase/react-native-firebase/issues/3671#event-3366923083
pr closed time in a day
delete branch invertase/react-native-firebase
delete branch : @dackers86/adding-debug-tasks
delete time in a day
push eventinvertase/react-native-firebase
commit sha 760adb05b2f6f4b694126d94ae6479c9d5466d18
docs(tests): added debug instructions for VSCode (#3612)
push time in a day
PR merged invertase/react-native-firebase
By default JS debugging can be difficult for the library through VS Code.
This updates the readme to provide clearer instructions on logging out errors and debugging using JS
pr closed time in a day
created taginvertase/react-native-firebase
🔥 A well-tested feature-rich modular Firebase implementation for React Native. Supports both iOS & Android platforms for all Firebase services.
created time in a day
created taginvertase/react-native-firebase
🔥 A well-tested feature-rich modular Firebase implementation for React Native. Supports both iOS & Android platforms for all Firebase services.
created time in a day
push eventinvertase/react-native-firebase
commit sha 9ba6487fdb458f70a54ff4431d650cc647487370
chore(release): release packages - @react-native-firebase/[email protected] - [email protected]
push time in a day
delete branch invertase/react-native-firebase
delete branch : @russell/crashlytics-methods
delete time in a day
push eventinvertase/react-native-firebase
commit sha 52eeed31b3436b0f90767298dcc515b0897ba942
feat(crashlytics): add new APIs `checkForUnsentReports`, `deleteUnsentReports`,`didCrashOnPreviousExecution`,`sendUnsentReports` (#4009) Adds the following additional Crashlytics APIs: - checkForUnsentReports() - deleteUnsentReports() - didCrashOnPreviousExecution() - sendUnsentReports() [publish] Co-authored-by: Mike Hardy <[email protected]> Co-authored-by: Mike Diarmid <[email protected]>
push time in a day
PR merged invertase/react-native-firebase
Description
Additional Crashlytics API, including:
- checkForUnsentReports()
- deleteUnsentReports()
- didCrashOnPreviousExecution()
- sendUnsentReports()
Notes
- I've created Android error messages for
checkForUnsentReportswhich I'm not sure about especially as there is no equivalent mechanism on the iOS side. I welcome thoughts on what to do about that.
Related issues
None that I'm aware of.
Checklist
- I read the Contributor Guide and followed the process outlined there for submitting PRs.
- [X] Yes
- My change supports the following platforms;
- [X]
Android - [X]
iOS
- [X]
- My change includes tests;
- [X]
e2etests added or updated inpackages/\*\*/e2e - [ ]
jesttests added or updated inpackages/\*\*/__tests__
- [X]
- [X] I have updated TypeScript types that are affected by my change.
- This is a breaking change;
- [ ] Yes
- [X] No
Test Plan
<!-- Demonstrate the code you've added is solid, e.g. test logs or screenshots. -->
Think react-native-firebase is great? Please consider supporting the project with any of the below:
- 👉 Star this repo on GitHub ⭐️
- 👉 Follow
React Native FirebaseandInvertaseon Twitter
pr closed time in a day
pull request commentinvertase/react-native-firebase
docs(messaging): Added custom xmpp server documentation example
spelling.json needs deleting - should not be committed, its a generated file used by CI - add to gitignore if it isn't already
comment created time in a day
Pull request review commentinvertase/react-native-firebase
docs(messaging): Added custom xmpp server documentation example
+---+title: Messaging with XMPP+description: To send and receive messages directly from devices with FCM requires you to create and deploy an XMPP server.+---++## Introduction++This is a reference for using the Firebase Messaging service to send and receive messages directly between devices. Although methods (e.g. `sendMessage()` are provided for sending and receiving message, additional configuration is needed to ensure a working solution for direct messaging from devices.++> A custom solution is needed to exchange messages directly between devices (including the message sender device)+> please ensure a solution from this article has been configured to successfully send and receive messages from a device.++The following describes how to set up a server to handle messages, including...++- A custom XMPP server with XCS for receiving messages.+- Firebase admin for sending messages.++So what are we going to do?++1. Send a message from a client device.+2. Intercept using a custom XMPP server.+3. Push the message to Firebase using firebase-admin+4. Receive the message and acknowledge on other connected devices.++## Why can't I send and receive messages?++A common instance involves an implementation similar to the following.++```js+firebase.messaging().onMessage(message => {+ console.log('Received a message');+});++firebase.messaging().onMessageSent(message => {+ console.log('Sent a message');+});++firebase.messaging().onSendError(message => {+ console.log('Received an Error');+});++firebase.messaging().sendMessage({+ data: {+ foo: 'bar',+ },+});+```++Although correct, none of the listeners will acknowledge a `message` or `error`.++Permissions are limited on the client meaning an additional solution is required to communicate between `FCM` and any connected devices.++## How do I receive messages?++This is where you will need to deploy a custom server based, for example one based on Node XCS++Below is an example of how to configure a custom XMPP server using `node-xcs`.++```js+const Sender = require('node-xcs').Sender;++async function operation() {+ return new Promise((resolve, reject) => {+ console.log('Listening >>>');++ // Enter firebase credentials here. {SenderID, ServerKey}+ var xcs = new Sender('XXXXXXXX', 'XXXXXXXX');++ xcs.start();++ xcs.on('message', function(messageId, from, data, category) {+ console.log('received message', messageId, from, data, category);+ });++ xcs.on('receipt', function(messageId, from, data, category) {+ console.log('received receipt', arguments);+ });++ xcs.on('error', e => console.warn('XMPP error.', e));+ });+}++async function app() {+ await operation();+}++app();+```++## How do I send messages?++An ability to post to firebase with the correct permissions, for this we can use `Firebase-admin`.
For sending messages we can use the Firebase Admin SDK.
comment created time in a day
Pull request review commentinvertase/react-native-firebase
docs(messaging): Added custom xmpp server documentation example
+---+title: Messaging with XMPP+description: To send and receive messages directly from devices with FCM requires you to create and deploy an XMPP server.+---++## Introduction++This is a reference for using the Firebase Messaging service to send and receive messages directly between devices. Although methods (e.g. `sendMessage()` are provided for sending and receiving message, additional configuration is needed to ensure a working solution for direct messaging from devices.++> A custom solution is needed to exchange messages directly between devices (including the message sender device)+> please ensure a solution from this article has been configured to successfully send and receive messages from a device.++The following describes how to set up a server to handle messages, including...++- A custom XMPP server with XCS for receiving messages.+- Firebase admin for sending messages.++So what are we going to do?++1. Send a message from a client device.+2. Intercept using a custom XMPP server.+3. Push the message to Firebase using firebase-admin+4. Receive the message and acknowledge on other connected devices.++## Why can't I send and receive messages?
This section could cause confusion, it says non of these listeners will acknowledge a message or error - but they do? And also these methods work for non device to server communication so I think the distinction needs to be cleared up.
Alternatively just have this step show how to do 1. Send a message from a client device. as per your bulleted points above, rather than all the extra bits.
comment created time in a day
push eventinvertase/react-native-firebase
commit sha 07895bef0e13ec29c04b1a82a28500228732c28b
chore(release): release packages - @react-native-firebase/[email protected] - @react-native-firebase/[email protected] - @react-native-firebase/[email protected] - @react-native-firebase/[email protected] - @react-native-firebase/[email protected] - @react-native-firebase/[email protected] - @react-native-firebase/[email protected] - @react-native-firebase/[email protected] - @react-native-firebase/[email protected] - @react-native-firebase/[email protected] - @react-native-firebase/[email protected] - @react-native-firebase/[email protected] - @react-native-firebase/[email protected] - @react-native-firebase/[email protected] - @react-native-firebase/[email protected] - @react-native-firebase/[email protected] - [email protected]
push time in a day
Pull request review commentinvertase/react-native-firebase
docs(messaging): Added custom xmpp server documentation example
+---+title: Messaging with XMPP+description: To send and receive messages directly from devices with FCM requires you to create and deploy an XMPP server.+---++## Introduction++This is a reference for using the Firebase Messaging service to send and receive messages directly between devices. Although methods (e.g. `sendMessage()` are provided for sending and receiving message, additional configuration is needed to ensure a working solution for direct messaging from devices.++> A custom solution is needed to exchange messages directly between devices (including the message sender device)
> A custom solution is **only required** if plan to exchange messages directly between devices (including the message sender device)
comment created time in a day
Pull request review commentinvertase/react-native-firebase
docs(messaging): Added custom xmpp server documentation example
cd ios/ && pod install > iOS requires further configuration before you can start receiving and sending > messages through Firebase. Read the documentation on how to [setup iOS with Firebase Cloud Messaging](/messaging/usage/ios-setup). +> use of the `sendMessage()` API and it's associated listeners requires a custom `XMPP` server. Read the documentation on how to [Messaging with XMPP](/messaging/usage/messaging-with-xmpp).
> Use of the `sendMessage()` API and it's associated listeners requires a custom `XMPP` server. Read the documentation on how to [Messaging with XMPP](/messaging/usage/messaging-with-xmpp).
comment created time in a day
push eventinvertase/react-native-firebase
commit sha bc7c51a547daef5e34c752077d6056bb034684f8
chore(release): release packages - @react-native-firebase/[email protected] - @react-native-firebase/[email protected] - @react-native-firebase/[email protected] - @react-native-firebase/[email protected] - @react-native-firebase/[email protected] - @react-native-firebase/[email protected] - @react-native-firebase/[email protected] - @react-native-firebase/[email protected] - @react-native-firebase/[email protected] - @react-native-firebase/[email protected] - @react-native-firebase/[email protected] - @react-native-firebase/[email protected] - @react-native-firebase/[email protected] - @react-native-firebase/[email protected] - @react-native-firebase/[email protected] - @react-native-firebase/[email protected] - @react-native-firebase/[email protected] - @react-native-firebase/[email protected] - [email protected]
commit sha 5063ee4e3cc63f14fef212b00a9fce5b4e1b3f02
build(admob): update core peer dependency to v8.3.0 [publish]
commit sha 7d754db0c8d44698fd8feb22a1c649f0481c1112
build(analytics): update core peer dependency to v8.3.0 [publish]
commit sha a9263d29d09d690071a11b7c79a8607c95f26ede
build(auth): update core peer dependency to v8.3.0 [publish]
commit sha 581e2ea605db8b8c9bbe80a0b58a672d6720258b
build(crashlytics): update core peer dependency to v8.3.0 [publish]
commit sha ad6378aada3f4cb97343a9040cbce470490999fd
build(database): update core peer dependency to v8.3.0 [publish]
commit sha 5fd30e141faa9afc82839a4baa67ca4871919d0d
build(dynamic-links): update core peer dependency to v8.3.0 [publish]
commit sha e9739ea00a556c8af8bffe25977ec8afe2001482
build(firestore): update core peer dependency to v8.3.0 [publish]
commit sha 4148fe40afe2f501d9d0c782861aecaeae101f5e
build(functions): update core peer dependency to v8.3.0 [publish]
commit sha eaf84139e463ec0d821a7b24ae3ea4992aa3721a
build(iid): update core peer dependency to v8.3.0 [publish]
commit sha 4ebcf518cf97d6c4bb0b770580cb4564824b7b30
build(in-app-messaging): update core peer dependency to v8.3.0 [publish]
commit sha e964b54c83e464ebad73bf527833084a8c2977c8
build(messaging): update core peer dependency to v8.3.0 [publish]
commit sha 8c5b9c9aaf5fc9f00691d5f387dc124f1fb575ee
build(ml-natural-language): update core peer dependency to v8.3.0 [publish]
commit sha 4f1762255dfd45bf6dd2a102c663c8c5379d94b7
build(ml-vision): update core peer dependency to v8.3.0 [publish]
commit sha 5f724c30e6d51b8564cc0b0e764adce8bdc10bcb
build(perf): update core peer dependency to v8.3.0 [publish]
commit sha 3cc0fb34a6d9629ecebdd3baf1590e84de4f4249
build(remote-config): update core peer dependency to v8.3.0 [publish]
commit sha 6d7a40422a3b6f36c775a7689cc508174e25fc19
build(storage): update core peer dependency to v8.3.0 [publish]
push time in a day
Pull request review commentinvertase/react-native-firebase
docs(messaging): Added custom xmpp server documentation example
+---+title: Messaging with XMPP+description: To send and receive messages with FCM requires additional steps to ensure listeners are correctly working.+---
Still needs fixing & @dackers86
comment created time in a day
Pull request review commentinvertase/react-native-firebase
docs(messaging): Added custom xmpp server documentation example
+---+title: Messaging with XMPP+description: To send and receive messages directly from devices with FCM requires you to create and deploy an XMPP server.
description: Send and receive FCM messages directly between devices & your server with a XMPP server.
comment created time in a day
push eventinvertase/react-native-firebase
commit sha 04d35175ffafbb4f3ac0de653fd72405d3be3773
Update docs/messaging/usage/messaging-with-xmpp.md Co-authored-by: Mike Hardy <[email protected]>
push time in a day
push eventinvertase/react-native-firebase
commit sha ce39abf9c0affe00ea13e2ad1580ac42bbb54a30
fix(messaging): added missing `from` property in Remote Message type (#4030) [publish] Co-authored-by: Mike Diarmid <[email protected]>
push time in a day
PR merged invertase/react-native-firebase
Description
I believe the from property was accidentally omitted from the FirebaseMessagingType.RemoteMessage interface. I've added it following the standards set by the rest of the properties.
Checklist
- I read the Contributor Guide and followed the process outlined there for submitting PRs.
- [x] Yes
- My change supports the following platforms;
- [x]
Android - [x]
iOS
- [x]
- My change includes tests;
- [ ]
e2etests added or updated inpackages/\*\*/e2e - [ ]
jesttests added or updated inpackages/\*\*/__tests__
- [ ]
- [x] I have updated TypeScript types that are affected by my change.
- This is a breaking change;
- [ ] Yes
- [x] No
pr closed time in a day
push eventemeraldsanto/react-native-firebase
commit sha 9efa57aae53a5febb34d7ed76e4f9832e189e063
Update packages/messaging/lib/index.d.ts
push time in a day
push eventemeraldsanto/react-native-firebase
commit sha e3de4b66b532cedcc963bb78f32900f4571102c8
Update packages/messaging/lib/index.d.ts
push time in a day
push eventemeraldsanto/react-native-firebase
commit sha 1af11f8c70f0936ad44c034a8e703e4f2d329835
Update packages/messaging/lib/index.d.ts
push time in a day
push eventemeraldsanto/react-native-firebase
commit sha 58a3429d297af63b15a13cf621efede8f34ea3c2
Update packages/messaging/lib/index.d.ts
push time in a day
Pull request review commentinvertase/react-native-firebase
[Cloud Messaging] Added missing `from` property in Remote Message type
export namespace FirebaseMessagingTypes { * The message type of the message. */ messageType?: string;-+ + /**+ * The topic name or message identifier.+ */
*/
comment created time in a day
Pull request review commentinvertase/react-native-firebase
[Cloud Messaging] Added missing `from` property in Remote Message type
export namespace FirebaseMessagingTypes { * The message type of the message. */ messageType?: string;-+
comment created time in a day
Pull request review commentinvertase/react-native-firebase
[Cloud Messaging] Added missing `from` property in Remote Message type
export namespace FirebaseMessagingTypes { * The message type of the message. */ messageType?: string;-+ + /**+ * The topic name or message identifier.
* The topic name or message identifier.
comment created time in a day
Pull request review commentinvertase/react-native-firebase
[Cloud Messaging] Added missing `from` property in Remote Message type
export namespace FirebaseMessagingTypes { * The message type of the message. */ messageType?: string;-+ + /**+ * The topic name or message identifier.+ */+ from?: string;+
comment created time in a day
pull request commentinvertase/react-native-firebase
[Cloud Messaging] Added missing `from` property in Remote Message type
@mikehardy - gets created on Native side only; https://github.com/invertase/react-native-firebase/blob/master/packages/messaging/android/src/main/java/io/invertase/firebase/messaging/ReactNativeFirebaseMessagingSerializer.java#L67-L69 does it exist though!
comment created time in a day
issue commentFirebaseExtended/flutterfire
@Bilonik Amazing work!!!, just waiting for Messaging to Upgrade 😁
A Messaging pre-release has just been published 🙃
https://firebase.flutter.dev/docs/messaging/overview
comment created time in 3 days
push eventFirebaseExtended/flutterfire
commit sha 4ed7e747abe5cf920ad19c019db1e329b67025cb
Deploy website - based on eef0e0d178278f28b18ce46606fe42a93484e2aa
push time in 3 days
push eventFirebaseExtended/flutterfire
commit sha eef0e0d178278f28b18ce46606fe42a93484e2aa
chore(firebase_messaging): migrate to depend on new `firebase_core` plugin (#3071)
push time in 3 days
delete branch FirebaseExtended/flutterfire
delete branch : @invertase/messaging-migration
delete time in 3 days
PR merged FirebaseExtended/flutterfire
Description
- Depend on
firebase_corepre-release versions and migrate plugin to usefirebase_corenative SDK versioning features;- Firebase iOS SDK versions are now locked to use the same version defined in
firebase_core. - Firebase Android SDK versions are now using the Firebase Bill of Materials (BoM) to specify individual SDK versions. BoM version is also sourced from
firebase_core.
- Firebase iOS SDK versions are now locked to use the same version defined in
- Allow iOS to be imported as a module.
Related Issues
N/A
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.
- [x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
- [x] If the pull request affects only one plugin, the PR title starts with the name of the plugin in brackets (e.g. [cloud_firestore])
- [x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See [Contributor Guide]).
- [x] All existing and new tests are passing.
- [x] I updated/added relevant documentation (doc comments with
///). - [x] The analyzer (
flutter analyze) does not report any problems on my PR. - [x] I read and followed the [Flutter Style Guide].
- [x] I updated pubspec.yaml with an appropriate new version according to the [pub versioning philosophy].
- [x] I updated CHANGELOG.md to add a description of the change.
- [x] I signed the [CLA].
- [x] I am willing to follow-up on review comments in a timely manner.
Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?
- [ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
- [x] No, this is not a breaking change.
<!-- Links --> [issue database]: https://github.com/flutter/flutter/issues [Contributor Guide]: https://github.com/FirebaseExtended/flutterfire/blob/master/CONTRIBUTING.md [Flutter Style Guide]: https://github.com/flutter/flutter/wiki/Style-guide-for-Flutter-repo [pub versioning philosophy]: https://www.dartlang.org/tools/pub/versioning [CLA]: https://cla.developers.google.com/
pr closed time in 3 days
push eventFirebaseExtended/flutterfire
commit sha 4d0a1b573538d5caa605c52e9c9fe6682eee36b0
docs(firebase_messaging): update change log
push time in 4 days
push eventFirebaseExtended/flutterfire
commit sha 0de0a0f40898f6cb97c8947e2615377cac4ddaba
feat(firebase_messaging): allow iOS to be imported as a module
commit sha fb859f234509167a24a75fcd4c88101ec2ee23f4
refactor(firebase_messaging): add Android FlutterFirebaseCorePlugin to MainActivity
push time in 4 days
PR opened FirebaseExtended/flutterfire
Description
Replace this paragraph with a description of what this PR is doing. If you're modifying existing behavior, describe the existing behavior, how this PR is changing it, and what motivated the change.
Related Issues
Replace this paragraph with a list of issues related to this PR from the issue database. Indicate, which of these issues are resolved or fixed by this PR. Note that you'll have to prefix the issue numbers with flutter/flutter#.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.
- [x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
- [x] If the pull request affects only one plugin, the PR title starts with the name of the plugin in brackets (e.g. [cloud_firestore])
- [x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See [Contributor Guide]).
- [ ] All existing and new tests are passing.
- [x] I updated/added relevant documentation (doc comments with
///). - [x] The analyzer (
flutter analyze) does not report any problems on my PR. - [x] I read and followed the [Flutter Style Guide].
- [x] I updated pubspec.yaml with an appropriate new version according to the [pub versioning philosophy].
- [ ] I updated CHANGELOG.md to add a description of the change.
- [x] I signed the [CLA].
- [x] I am willing to follow-up on review comments in a timely manner.
Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?
- [ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
- [x] No, this is not a breaking change.
<!-- Links --> [issue database]: https://github.com/flutter/flutter/issues [Contributor Guide]: https://github.com/FirebaseExtended/flutterfire/blob/master/CONTRIBUTING.md [Flutter Style Guide]: https://github.com/flutter/flutter/wiki/Style-guide-for-Flutter-repo [pub versioning philosophy]: https://www.dartlang.org/tools/pub/versioning [CLA]: https://cla.developers.google.com/
pr created time in 4 days
create barnchFirebaseExtended/flutterfire
branch : @invertase/messaging-migration
created branch time in 4 days
issue closedFirebaseExtended/flutterfire
Adding firebase_database to Flutter project also add Firebase Analytics
I integrated Firebase DB to my Flutter app by adding firebase_database package to pubspec.yaml and also import the GoogleService-Info.plist. (I did set Analytics to NO when ask in the firebase web console)
I am now constantly seeing this in my Android Studio console when running simulator: 6.25.0 - [Firebase/Analytics][I-ACS023130] Configuration not found. Using default configuration
I am also noticing that Podfile.lock now included bunch of packages from Firebase and Google. To name a few from the list:
- firebase_core_web
- firebaseAnalytics
- FirebaseAuthInterop
- FirebaseCoreDisgnostics
- FirebaseInstallations
- GoogleAppMeasurement
- GoogleDataTransport
- GoogleUtilities/UserDefaults
- GoogleUtilities/Reachability
Are all these packages needed just for using Firebase DB? How to disable the Firebase/Analytics? (In GoogleService-info.plist IS_ANALYTICS_ENABLED is set to NO)
closed time in 4 days
jackkongjj
issue commentFirebaseExtended/flutterfire
Adding firebase_database to Flutter project also add Firebase Analytics
Hey the latest pre-release of Database now uses the CoreOnly pod on iOS/MacOS - so analytics should no longer be added now. Please give it a try, thanks!
https://firebase.flutter.dev/docs/database/overview
comment created time in 4 days
issue closedFirebaseExtended/flutterfire
Currently there is no support for Flutter macOS
Remote Config is a Key firebase feature that should be cross platform supported.
closed time in 4 days
AndroidNils
issue commentFirebaseExtended/flutterfire
MacOS support for Remote Config has landed on master and a pre-release is available, so I'm going to go ahead and close this issue now, thanks everyone!
https://firebase.flutter.dev/docs/remote-config/overview
comment created time in 4 days
PR closed FirebaseExtended/flutterfire
Description
Adds macOS support to the firebase_remote_config plugin
Related Issues
Fixes FirebaseExtended/flutterfire#2697, also related to FirebaseExtended/flutterfire#1653
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.
- [x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
- [x] If the pull request affects only one plugin, the PR title starts with the name of the plugin in brackets (e.g. [cloud_firestore])
- [x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See [Contributor Guide]).
- [x] All existing and new tests are passing.
- [x] I updated/added relevant documentation (doc comments with
///). - [x] The analyzer (
flutter analyze) does not report any problems on my PR. - [x] I read and followed the [Flutter Style Guide].
- [x] I updated pubspec.yaml with an appropriate new version according to the [pub versioning philosophy].
- [x] I updated CHANGELOG.md to add a description of the change.
- [x] I signed the [CLA].
- [x] I am willing to follow-up on review comments in a timely manner.
Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?
- [ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
- [x] No, this is not a breaking change.
<!-- Links --> [issue database]: https://github.com/flutter/flutter/issues [Contributor Guide]: https://github.com/FirebaseExtended/flutterfire/blob/master/CONTRIBUTING.md [Flutter Style Guide]: https://github.com/flutter/flutter/wiki/Style-guide-for-Flutter-repo [pub versioning philosophy]: https://www.dartlang.org/tools/pub/versioning [CLA]: https://cla.developers.google.com/
pr closed time in 4 days
pull request commentFirebaseExtended/flutterfire
[firebase_remote_config] Add macOS support
MacOS support for Remote Config has landed on master from another PR of mine and a pre-release is available, so I'm going to go ahead and close this PR, sorry 🙈 thanks for contributing though!
https://firebase.flutter.dev/docs/remote-config/overview
comment created time in 4 days
issue commentFirebaseExtended/flutterfire
Remote Config with new firebase_core (pre-rework) pre-release is up, also added in MacOS support whilst I was at it. 🙃
https://firebase.flutter.dev/docs/remote-config/overview
comment created time in 4 days
issue closedFirebaseExtended/flutterfire
Building Flutter app with both cloud_firestore 0.14.0-dev.1 (latest at the time) and firebase_auth 0.16.1 (latest at the time) is not possible.
Steps to reproduce the behavior:
- Create new Flutter app
- Set the following dependencies in pubspec.yaml
dependencies:
flutter:
sdk: flutter
firebase_auth: "0.16.1"
flutter_auth_buttons: ^0.8.0
Expected behavior
Run flutter pub get will finish successfully.
Actual behavior
The is the result of running flutter pub get:
[frontend] flutter pub get
Running "flutter pub get" in frontend...
Because cloud_firestore >=0.14.0-dev.1 depends on firebase_core ^0.5.0-dev.1 and firebase_auth 0.16.1 depends on firebase_core ^0.4.4, cloud_firestore >=0.14.0-dev.1 is incompatible with firebase_auth 0.16.1.
So, because frontend depends on both firebase_auth 0.16.1 and cloud_firestore 0.14.0-dev.1, version solving failed.
pub get failed (1; So, because frontend depends on both firebase_auth 0.16.1 and cloud_firestore 0.14.0-dev.1, version solving failed.)
exit code 1
Additional context I'm trying to use the latest (in development) FireStore version in Flutter app for web. I'm using the development version in order to use the emulator.
Flutter doctor
Run flutter doctor and paste the output below:
flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel beta, 1.20.0-7.2.pre, on Microsoft Windows [Version 10.0.18363.959], locale en-IL)
[X] Android toolchain - develop for Android devices
X Unable to locate Android SDK.
Install Android Studio from: https://developer.android.com/studio/index.html
On first launch it will assist you in installing the Android SDK components.
(or visit https://flutter.dev/docs/get-started/install/windows#android-setup for detailed instructions).
If the Android SDK has been installed to a custom location, set ANDROID_SDK_ROOT to that location.
You may also want to add it to your PATH environment variable.
[√] Chrome - develop for the web
[!] Android Studio (not installed)
[√] VS Code, 64-bit edition (version 1.47.2)
[√] Connected device (3 available)
! Doctor found issues in 2 categories.
closed time in 4 days
ido-ran
issue commentFirebaseExtended/flutterfire
As above, these are now published - thanks 👍
comment created time in 4 days
push eventFirebaseExtended/flutterfire
commit sha a44e7aeb0521b1dd197944b48da15ca2119dabbe
docs(website): hide unavailable plugins
commit sha adbe068a478b7384d5fcb9c644591ba3993a240f
docs(website): fix macos support flag using incorrect variable
push time in 4 days
push eventFirebaseExtended/flutterfire
commit sha 63be6a4cd4e2fd69b599f1e05dcc8d55f82f9d74
Deploy website - based on 83d4183b79d2953736df06629140126e3eb5a421
push time in 4 days
push eventFirebaseExtended/flutterfire
commit sha 7f876f4bfdcde8600a190bd3a6baf8345d8b3acc
Deploy website - based on 83d4183b79d2953736df06629140126e3eb5a421
push time in 4 days
push eventFirebaseExtended/flutterfire
commit sha 4ff7f51e85388bf0b50660be32a1b034a00b3d3b
Deploy website - based on 83d4183b79d2953736df06629140126e3eb5a421
push time in 4 days
push eventFirebaseExtended/flutterfire
commit sha f88345f8a8f06dc0f134ca5edf1712d20d6c7692
Deploy website - based on 83d4183b79d2953736df06629140126e3eb5a421
push time in 4 days
push eventFirebaseExtended/flutterfire
commit sha 88e068596f964ebc20f795075a4218d8f9f51935
chore(firebase_remote_config): depend on new `firebase_core` pre-release
commit sha 5a8beb88c877900faf5b2394f5050cf52380d374
feat(firebase_remote_config): use new iOS Firebase SDK versioning setup
commit sha 7ea2f337f5056e2b3711657070abad357e5ddc21
feat(firebase_remote_config): allow iOS to be imported as a module
commit sha 28553c80c626815810c968d1f878a23531c6d1a9
refactor(firebase_remote_config): don't configure iOS FIRApp instance This is now automatically handled by the `firebase_core` plugin.
commit sha 3cc632216985b288756f21f4087f67967b9909d2
feat(firebase_remote_config): add support for MacOS
commit sha 7316eaac716bb7a9fc73b2084e0ffff4d226b301
chore(firebase_remote_config): add MacOS to example app
commit sha 680d5392542b1be46b2c6f6331e1c898e85d549b
feat(firebase_remote_config): use new Android Firebase SDK versioning setup
commit sha e587bf1076c2d645228057a975b25fb1befe210a
refactor(firebase_remote_config): update android plugin example to use v2 embedding
commit sha 8200730d5a2bdb0c973a309b39a71e1cf1a61917
docs(cloud_storage): remove empty usage page from sidebar
commit sha d7ea99607c80767b3511aa82214ca61f27f1ec33
docs(firebase_remote_config): add plugin summary page & sidebar link
commit sha 26f3b2e1f146de24df051325e60239e2028c2da8
tests(firebase_remote_config): setup CI workflow
commit sha 77909ddb6af5e21823067cde6e6045b16ec65d60
refactor(firebase_remote_config): update e2e tests to use Core
commit sha 790c4d292c0c690088d7f629edc2527fd4b2ee71
docs(firebase_remote_config): add CI badge to readme
commit sha d98dff842ffd7d713ed959c77e427ebc2fb42a08
tests(*): update remaining CI workflows to use scripts & add make certain jobs conditional
commit sha 83d4183b79d2953736df06629140126e3eb5a421
chore(firebase_remote_config): migrate to use new `firebase_core` (#3066)
push time in 4 days
delete branch FirebaseExtended/flutterfire
delete branch : @invertase/core-migration-2
delete time in 4 days
PR merged FirebaseExtended/flutterfire
Description
- Depend on new
firebase_core(pre-release). - Firebase iOS SDK versions are now locked to use the same version defined in
firebase_core. - Firebase Android SDK versions are now using the Firebase Bill of Materials (BoM)
to specify individual SDK versions. BoM version is also sourced from
firebase_core. - Added support for MacOS. (#1653)
- Allow iOS & MacOS plugins to be imported as modules.
Related Issues
Replace this paragraph with a list of issues related to this PR from the issue database. Indicate, which of these issues are resolved or fixed by this PR. Note that you'll have to prefix the issue numbers with flutter/flutter#.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.
- [x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
- [x] If the pull request affects only one plugin, the PR title starts with the name of the plugin in brackets (e.g. [cloud_firestore])
- [x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See [Contributor Guide]).
- [ ] All existing and new tests are passing.
- [x] I updated/added relevant documentation (doc comments with
///). - [x] The analyzer (
flutter analyze) does not report any problems on my PR. - [x] I read and followed the [Flutter Style Guide].
- [x] I updated pubspec.yaml with an appropriate new version according to the [pub versioning philosophy].
- [x] I updated CHANGELOG.md to add a description of the change.
- [x] I signed the [CLA].
- [x] I am willing to follow-up on review comments in a timely manner.
Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?
- [ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
- [x] No, this is not a breaking change.
Local Testing
Android & iOS:
MacOS:
<!-- Links --> [issue database]: https://github.com/flutter/flutter/issues [Contributor Guide]: https://github.com/FirebaseExtended/flutterfire/blob/master/CONTRIBUTING.md [Flutter Style Guide]: https://github.com/flutter/flutter/wiki/Style-guide-for-Flutter-repo [pub versioning philosophy]: https://www.dartlang.org/tools/pub/versioning [CLA]: https://cla.developers.google.com/
pr closed time in 4 days
push eventFirebaseExtended/flutterfire
commit sha 790c4d292c0c690088d7f629edc2527fd4b2ee71
docs(firebase_remote_config): add CI badge to readme
commit sha d98dff842ffd7d713ed959c77e427ebc2fb42a08
tests(*): update remaining CI workflows to use scripts & add make certain jobs conditional
push time in 4 days
push eventFirebaseExtended/flutterfire
commit sha 77909ddb6af5e21823067cde6e6045b16ec65d60
refactor(firebase_remote_config): update e2e tests to use Core
push time in 4 days
issue commentFirebaseExtended/flutterfire
Hey all, another FYI 🙃 firebase_remote_config MacOS support is landing shortly via #3066
comment created time in 4 days
PR opened FirebaseExtended/flutterfire
Description
- Depend on new
firebase_core(pre-release). - Firebase iOS SDK versions are now locked to use the same version defined in
firebase_core. - Firebase Android SDK versions are now using the Firebase Bill of Materials (BoM)
to specify individual SDK versions. BoM version is also sourced from
firebase_core. - Added support for MacOS. (#1653)
- Allow iOS & MacOS plugins to be imported as modules.
Related Issues
Replace this paragraph with a list of issues related to this PR from the issue database. Indicate, which of these issues are resolved or fixed by this PR. Note that you'll have to prefix the issue numbers with flutter/flutter#.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.
- [x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
- [x] If the pull request affects only one plugin, the PR title starts with the name of the plugin in brackets (e.g. [cloud_firestore])
- [x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See [Contributor Guide]).
- [ ] All existing and new tests are passing.
- [x] I updated/added relevant documentation (doc comments with
///). - [x] The analyzer (
flutter analyze) does not report any problems on my PR. - [x] I read and followed the [Flutter Style Guide].
- [x] I updated pubspec.yaml with an appropriate new version according to the [pub versioning philosophy].
- [x] I updated CHANGELOG.md to add a description of the change.
- [x] I signed the [CLA].
- [x] I am willing to follow-up on review comments in a timely manner.
Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?
- [ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
- [x] No, this is not a breaking change.
Local Testing
Android & iOS:
MacOS:
<!-- Links --> [issue database]: https://github.com/flutter/flutter/issues [Contributor Guide]: https://github.com/FirebaseExtended/flutterfire/blob/master/CONTRIBUTING.md [Flutter Style Guide]: https://github.com/flutter/flutter/wiki/Style-guide-for-Flutter-repo [pub versioning philosophy]: https://www.dartlang.org/tools/pub/versioning [CLA]: https://cla.developers.google.com/
pr created time in 4 days
push eventFirebaseExtended/flutterfire
commit sha 0fef48fc2dc37b59b984baf79a0a9d30cf5876f7
docs(core): fix secondary apps Firestore example
commit sha 19e7f1643e1ca90cc4d279fee273aec39b3b9e06
docs(cloud_firestore): fix settings examples
commit sha 8002e178cef67f343f8b59fb0e1a8d2ab3899e34
docs(cloud_firestore): update usage examples (#3062)
commit sha 88e068596f964ebc20f795075a4218d8f9f51935
chore(firebase_remote_config): depend on new `firebase_core` pre-release
commit sha 5a8beb88c877900faf5b2394f5050cf52380d374
feat(firebase_remote_config): use new iOS Firebase SDK versioning setup
commit sha 7ea2f337f5056e2b3711657070abad357e5ddc21
feat(firebase_remote_config): allow iOS to be imported as a module
commit sha 28553c80c626815810c968d1f878a23531c6d1a9
refactor(firebase_remote_config): don't configure iOS FIRApp instance This is now automatically handled by the `firebase_core` plugin.
commit sha 3cc632216985b288756f21f4087f67967b9909d2
feat(firebase_remote_config): add support for MacOS
commit sha 7316eaac716bb7a9fc73b2084e0ffff4d226b301
chore(firebase_remote_config): add MacOS to example app
commit sha 680d5392542b1be46b2c6f6331e1c898e85d549b
feat(firebase_remote_config): use new Android Firebase SDK versioning setup
commit sha e587bf1076c2d645228057a975b25fb1befe210a
refactor(firebase_remote_config): update android plugin example to use v2 embedding
commit sha 8200730d5a2bdb0c973a309b39a71e1cf1a61917
docs(cloud_storage): remove empty usage page from sidebar
commit sha d7ea99607c80767b3511aa82214ca61f27f1ec33
docs(firebase_remote_config): add plugin summary page & sidebar link
commit sha 26f3b2e1f146de24df051325e60239e2028c2da8
tests(firebase_remote_config): setup CI workflow
push time in 4 days
Pull request review commentinvertase/react-native-firebase
feat(crashlytics): additional API coverage
export namespace FirebaseCrashlyticsTypes { * */ isCrashlyticsCollectionEnabled: true;+ /**+ * Determines whether there are any unsent crash reports cached on the device. The callback only executes+ * if automatic data collection is disabled.+ *+ * #### Example+ *+ * ```js+ * async checkReports() {+ * // returns boolean value+ * const unsentReports = await firebase.crashlytics().checkForUnsentReports();+ * }+ *+ * checkReports();+ * ```+ *+ */+ checkForUnsentReports(): Promise<boolean>;+ /**+ * Deletes any unsent reports on the device. This method only applies if automatic data collection is+ * disabled.+ *+ * #### Example+ *+ * ```js+ * firebase.crashlytics().deleteUnsentReports();+ * ```+ *+ */+ deleteUnsentReports(): void;
deleteUnsentReports(): Promise<void>;
As the native call is async lets make this one return a Promise (JS method also needs updating)
comment created time in 4 days
Pull request review commentinvertase/react-native-firebase
feat(crashlytics): additional API coverage
PODS: - Firebase/MLVisionTextModel (= 6.28.1) - React - RNFBApp- - RNFBPerf (7.2.2):+ - RNFBPerf (7.2.3): - Firebase/Performance (= 6.28.1) - React - RNFBApp- - RNFBRemoteConfig (7.2.2):+ - RNFBRemoteConfig (8.0.0):
RNFB pod versions are importing the package.json file and reading the version from there, no manual updates necessary. pod install in the tests/ios directory is all that is needed
comment created time in 4 days
issue commentFirebaseExtended/flutterfire
@Salakar Great work ... but you neglected to mention Crashlytics ?
For Crashlytics see https://github.com/FirebaseExtended/flutterfire/pull/2288#issuecomment-663170672
comment created time in 4 days
issue commentFirebaseExtended/flutterfire
Hey everyone; another quick update;
The following pre-release versions are now live - these have all been updated to work with new Core (including CI & testing improvements for each):
- Core (rework version)
- Firestore (rework version)
- Auth (pre-rework version)
- Analytics (pre-rework version)
- Database (pre-rework version)
- Functions (pre-rework version)
- Storage (pre-rework version)
- Performance Monitoring (pre-rework version)
Lots of work has gone into each of these plugins to improve testing & CI stability, these are now all using the latest Firebase SDKS and are also using the shared Firebase SDK versioning setup meaning all these plugins now depend on the same version of the Firebase SDKs - no longer mixing & matching versions.
If you can; please give these a try - overview pages for each of these are now showing on the docs site including a quick installation guide which shows what the latest pre-release version for each is, e.g. Analytics: https://firebase.flutter.dev/docs/analytics/overview.
Remote Config, Links, In App Messaging and Messaging pre-releases that use the new Core will be available soon.
comment created time in 5 days
push eventFirebaseExtended/flutterfire
commit sha a0f53f90d1614d097042c7c98b1bab6f1291f3a6
Deploy website - based on 8002e178cef67f343f8b59fb0e1a8d2ab3899e34
push time in 5 days
push eventFirebaseExtended/flutterfire
commit sha 0fef48fc2dc37b59b984baf79a0a9d30cf5876f7
docs(core): fix secondary apps Firestore example
commit sha 19e7f1643e1ca90cc4d279fee273aec39b3b9e06
docs(cloud_firestore): fix settings examples
commit sha 8002e178cef67f343f8b59fb0e1a8d2ab3899e34
docs(cloud_firestore): update usage examples (#3062)
push time in 5 days
delete branch FirebaseExtended/flutterfire
delete branch : @invertase/firestore-docs-update
delete time in 5 days
PR merged FirebaseExtended/flutterfire
Description
Fixes a couple of incorrect examples (API changed).
Related Issues
Replace this paragraph with a list of issues related to this PR from the issue database. Indicate, which of these issues are resolved or fixed by this PR. Note that you'll have to prefix the issue numbers with flutter/flutter#.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.
- [x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
- [x] If the pull request affects only one plugin, the PR title starts with the name of the plugin in brackets (e.g. [cloud_firestore])
- [ ] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See [Contributor Guide]).
- [ ] All existing and new tests are passing.
- [x] I updated/added relevant documentation (doc comments with
///). - [x] The analyzer (
flutter analyze) does not report any problems on my PR. - [x] I read and followed the [Flutter Style Guide].
- [ ] I updated pubspec.yaml with an appropriate new version according to the [pub versioning philosophy].
- [ ] I updated CHANGELOG.md to add a description of the change.
- [x] I signed the [CLA].
- [x] I am willing to follow-up on review comments in a timely manner.
Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?
- [ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
- [x] No, this is not a breaking change.
<!-- Links --> [issue database]: https://github.com/flutter/flutter/issues [Contributor Guide]: https://github.com/FirebaseExtended/flutterfire/blob/master/CONTRIBUTING.md [Flutter Style Guide]: https://github.com/flutter/flutter/wiki/Style-guide-for-Flutter-repo [pub versioning philosophy]: https://www.dartlang.org/tools/pub/versioning [CLA]: https://cla.developers.google.com/
pr closed time in 5 days
PR opened FirebaseExtended/flutterfire
Description
Replace this paragraph with a description of what this PR is doing. If you're modifying existing behavior, describe the existing behavior, how this PR is changing it, and what motivated the change.
Related Issues
Replace this paragraph with a list of issues related to this PR from the issue database. Indicate, which of these issues are resolved or fixed by this PR. Note that you'll have to prefix the issue numbers with flutter/flutter#.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.
- [ ] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
- [ ] If the pull request affects only one plugin, the PR title starts with the name of the plugin in brackets (e.g. [cloud_firestore])
- [ ] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See [Contributor Guide]).
- [ ] All existing and new tests are passing.
- [ ] I updated/added relevant documentation (doc comments with
///). - [ ] The analyzer (
flutter analyze) does not report any problems on my PR. - [ ] I read and followed the [Flutter Style Guide].
- [ ] I updated pubspec.yaml with an appropriate new version according to the [pub versioning philosophy].
- [ ] I updated CHANGELOG.md to add a description of the change.
- [ ] I signed the [CLA].
- [ ] I am willing to follow-up on review comments in a timely manner.
Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?
- [ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
- [ ] No, this is not a breaking change.
<!-- Links --> [issue database]: https://github.com/flutter/flutter/issues [Contributor Guide]: https://github.com/FirebaseExtended/flutterfire/blob/master/CONTRIBUTING.md [Flutter Style Guide]: https://github.com/flutter/flutter/wiki/Style-guide-for-Flutter-repo [pub versioning philosophy]: https://www.dartlang.org/tools/pub/versioning [CLA]: https://cla.developers.google.com/
pr created time in 5 days
push eventFirebaseExtended/flutterfire
commit sha 0fef48fc2dc37b59b984baf79a0a9d30cf5876f7
docs(core): fix secondary apps Firestore example
commit sha 19e7f1643e1ca90cc4d279fee273aec39b3b9e06
docs(cloud_firestore): fix settings examples
push time in 5 days
create barnchFirebaseExtended/flutterfire
branch : @invertase/firestore-docs-update
created branch time in 5 days
PR closed FirebaseExtended/flutterfire
Description
Replace this paragraph with a description of what this PR is doing. If you're modifying existing behavior, describe the existing behavior, how this PR is changing it, and what motivated the change.
Related Issues
Replace this paragraph with a list of issues related to this PR from the issue database. Indicate, which of these issues are resolved or fixed by this PR. Note that you'll have to prefix the issue numbers with flutter/flutter#.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.
- [ ] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
- [ ] If the pull request affects only one plugin, the PR title starts with the name of the plugin in brackets (e.g. [cloud_firestore])
- [ ] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See [Contributor Guide]).
- [ ] All existing and new tests are passing.
- [ ] I updated/added relevant documentation (doc comments with
///). - [ ] The analyzer (
flutter analyze) does not report any problems on my PR. - [ ] I read and followed the [Flutter Style Guide].
- [ ] I updated pubspec.yaml with an appropriate new version according to the [pub versioning philosophy].
- [ ] I updated CHANGELOG.md to add a description of the change.
- [ ] I signed the [CLA].
- [ ] I am willing to follow-up on review comments in a timely manner.
Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?
- [ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
- [ ] No, this is not a breaking change.
<!-- Links --> [issue database]: https://github.com/flutter/flutter/issues [Contributor Guide]: https://github.com/FirebaseExtended/flutterfire/blob/master/CONTRIBUTING.md [Flutter Style Guide]: https://github.com/flutter/flutter/wiki/Style-guide-for-Flutter-repo [pub versioning philosophy]: https://www.dartlang.org/tools/pub/versioning [CLA]: https://cla.developers.google.com/
pr closed time in 5 days
pull request commentFirebaseExtended/flutterfire
tests(cloud_firestore): enable Firestore emulator for web tests
Still not working, so going to close for now.
comment created time in 5 days
PR opened FirebaseExtended/flutterfire
Description
Replace this paragraph with a description of what this PR is doing. If you're modifying existing behavior, describe the existing behavior, how this PR is changing it, and what motivated the change.
Related Issues
Replace this paragraph with a list of issues related to this PR from the issue database. Indicate, which of these issues are resolved or fixed by this PR. Note that you'll have to prefix the issue numbers with flutter/flutter#.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.
- [ ] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
- [ ] If the pull request affects only one plugin, the PR title starts with the name of the plugin in brackets (e.g. [cloud_firestore])
- [ ] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See [Contributor Guide]).
- [ ] All existing and new tests are passing.
- [ ] I updated/added relevant documentation (doc comments with
///). - [ ] The analyzer (
flutter analyze) does not report any problems on my PR. - [ ] I read and followed the [Flutter Style Guide].
- [ ] I updated pubspec.yaml with an appropriate new version according to the [pub versioning philosophy].
- [ ] I updated CHANGELOG.md to add a description of the change.
- [ ] I signed the [CLA].
- [ ] I am willing to follow-up on review comments in a timely manner.
Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?
- [ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
- [ ] No, this is not a breaking change.
<!-- Links --> [issue database]: https://github.com/flutter/flutter/issues [Contributor Guide]: https://github.com/FirebaseExtended/flutterfire/blob/master/CONTRIBUTING.md [Flutter Style Guide]: https://github.com/flutter/flutter/wiki/Style-guide-for-Flutter-repo [pub versioning philosophy]: https://www.dartlang.org/tools/pub/versioning [CLA]: https://cla.developers.google.com/
pr created time in 5 days
push eventFirebaseExtended/flutterfire
commit sha 0d5b5e22a10e5386019b188c6c226c46d3901a1f
tests(cloud_firestore): enable Firestore emulator for web tests
push time in 5 days
create barnchFirebaseExtended/flutterfire
branch : @invertase/firestore-web-emulator
created branch time in 5 days
create barnchFirebaseExtended/flutterfire
branch : @invertase/core-migration-2
created branch time in 5 days
push eventFirebaseExtended/flutterfire
commit sha ac4d9fc3c594e1cab8823b14e3e3767d849d5594
Deploy website - based on 1be0300ae5626ceacaa73d55d3f47f752937db65
push time in 5 days
push eventFirebaseExtended/flutterfire
commit sha 1be0300ae5626ceacaa73d55d3f47f752937db65
docs: add CI badges to readme
push time in 5 days
push eventFirebaseExtended/flutterfire
commit sha e6d0a9d983a7a4214092121713111edbce9086ab
docs(firebase_database): update platform support table
commit sha d0127ad0c82553170f53b5675bc1465a13722aab
tests(firebase_performance): update workflow to use new scripts
commit sha 1f33b8e9cda6bdff13733e3a390b4129e368750a
tests(firebase_auth): update workflow to use new scripts
commit sha aed91f9f8f8ce483fd450a17296622b4da674836
tests: update drive script to remove no-build flag on macos
commit sha dc9bd330d7648c22f876acce3355cecb92df2562
tests(firebase_core): update workflow to use new scripts
commit sha 703d26c1786f9287b4d01ce0eb9e37d0d2c53131
tests(firebase_database): update workflow to use new scripts
commit sha b4ffae1472576687c393579a1330d6f2f50c70e5
tests(firebase_storage): update workflow to use new scripts
commit sha 89a0485cb4bd0658f5f3a7229233d13cd938ab45
docs(firebase_storage): update platform support table
commit sha 4d0ec597e09551a01ef9cfe086053881ab92a12d
tests(cloud_firestore): update workflow to use new scripts
commit sha 5c5219d7f04b412f72a5feca321200a27cd32f8c
tests: update CI workflows to use new scripts (#3060)
push time in 5 days
delete branch FirebaseExtended/flutterfire
delete branch : @invertase/ci-use-new-scripts
delete time in 5 days
PR merged FirebaseExtended/flutterfire
Description
Updates all workflows to use new CI scripts (which should also improve stability of testing).
Related Issues
N/A
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.
- [x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
- [] If the pull request affects only one plugin, the PR title starts with the name of the plugin in brackets (e.g. [cloud_firestore])
- [x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See [Contributor Guide]).
- [x] All existing and new tests are passing.
- [] I updated/added relevant documentation (doc comments with
///). - [x] The analyzer (
flutter analyze) does not report any problems on my PR. - [x] I read and followed the [Flutter Style Guide].
- [ ] I updated pubspec.yaml with an appropriate new version according to the [pub versioning philosophy].
- [ ] I updated CHANGELOG.md to add a description of the change.
- [x] I signed the [CLA].
- [x] I am willing to follow-up on review comments in a timely manner.
Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?
- [ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
- [x] No, this is not a breaking change.
<!-- Links --> [issue database]: https://github.com/flutter/flutter/issues [Contributor Guide]: https://github.com/FirebaseExtended/flutterfire/blob/master/CONTRIBUTING.md [Flutter Style Guide]: https://github.com/flutter/flutter/wiki/Style-guide-for-Flutter-repo [pub versioning philosophy]: https://www.dartlang.org/tools/pub/versioning [CLA]: https://cla.developers.google.com/
pr closed time in 5 days
push eventFirebaseExtended/flutterfire
commit sha 4d0ec597e09551a01ef9cfe086053881ab92a12d
tests(cloud_firestore): update workflow to use new scripts
push time in 5 days
PR closed FirebaseExtended/flutterfire
Bumps elliptic from 6.5.2 to 6.5.3. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/indutny/elliptic/commit/8647803dc3d90506aa03021737f7b061ba959ae1"><code>8647803</code></a> 6.5.3</li> <li><a href="https://github.com/indutny/elliptic/commit/856fe4d99fe7b6200556e6400b3bf585b1721bec"><code>856fe4d</code></a> signature: prevent malleability and overflows</li> <li>See full diff in <a href="https://github.com/indutny/elliptic/compare/v6.5.2...v6.5.3">compare view</a></li> </ul> </details> <br />
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
<details> <summary>Dependabot commands and options</summary> <br />
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)@dependabot use these labelswill set the current labels as the default for future PRs for this repo and language@dependabot use these reviewerswill set the current reviewers as the default for future PRs for this repo and language@dependabot use these assigneeswill set the current assignees as the default for future PRs for this repo and language@dependabot use this milestonewill set the current milestone as the default for future PRs for this repo and language
You can disable automated security fix PRs for this repo from the Security Alerts page.
</details>
pr closed time in 5 days
push eventFirebaseExtended/flutterfire
commit sha 1f33b8e9cda6bdff13733e3a390b4129e368750a
tests(firebase_auth): update workflow to use new scripts
commit sha aed91f9f8f8ce483fd450a17296622b4da674836
tests: update drive script to remove no-build flag on macos
commit sha dc9bd330d7648c22f876acce3355cecb92df2562
tests(firebase_core): update workflow to use new scripts
commit sha 703d26c1786f9287b4d01ce0eb9e37d0d2c53131
tests(firebase_database): update workflow to use new scripts
commit sha b4ffae1472576687c393579a1330d6f2f50c70e5
tests(firebase_storage): update workflow to use new scripts
commit sha 89a0485cb4bd0658f5f3a7229233d13cd938ab45
docs(firebase_storage): update platform support table
push time in 5 days
PR opened FirebaseExtended/flutterfire
Description
Replace this paragraph with a description of what this PR is doing. If you're modifying existing behavior, describe the existing behavior, how this PR is changing it, and what motivated the change.
Related Issues
Replace this paragraph with a list of issues related to this PR from the issue database. Indicate, which of these issues are resolved or fixed by this PR. Note that you'll have to prefix the issue numbers with flutter/flutter#.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.
- [ ] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
- [ ] If the pull request affects only one plugin, the PR title starts with the name of the plugin in brackets (e.g. [cloud_firestore])
- [ ] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See [Contributor Guide]).
- [ ] All existing and new tests are passing.
- [ ] I updated/added relevant documentation (doc comments with
///). - [ ] The analyzer (
flutter analyze) does not report any problems on my PR. - [ ] I read and followed the [Flutter Style Guide].
- [ ] I updated pubspec.yaml with an appropriate new version according to the [pub versioning philosophy].
- [ ] I updated CHANGELOG.md to add a description of the change.
- [ ] I signed the [CLA].
- [ ] I am willing to follow-up on review comments in a timely manner.
Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?
- [ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
- [ ] No, this is not a breaking change.
<!-- Links --> [issue database]: https://github.com/flutter/flutter/issues [Contributor Guide]: https://github.com/FirebaseExtended/flutterfire/blob/master/CONTRIBUTING.md [Flutter Style Guide]: https://github.com/flutter/flutter/wiki/Style-guide-for-Flutter-repo [pub versioning philosophy]: https://www.dartlang.org/tools/pub/versioning [CLA]: https://cla.developers.google.com/
pr created time in 5 days