Conversation
mehmetf
left a comment
There was a problem hiding this comment.
Is there a reason why categories is a no-no? How do we prevent them from popping up again.
The PR itself LGTM as it is just an implementation detail that does not leak to Dart API.
If there are multiple categories methods that have the same name in different plugins, and an APP imported all those plugins, when in run time, objective-c will pick up a random one and use it for all of the invocations. So it can break the project since the implementations of these same named category could be different. Details in here flutter/flutter#27960. |
Fixing [flutter/flutter#27361](flutter/flutter#27361) and [flutter/flutter#27960](flutter/flutter#27960) Used static c function instead of category. The plugins effected are cloud_firestore firebase_admob firebase_auth firebase_core firebase_database firebase_dynamiclink firebase_mlvision firebase_storage google_signin camera
This reverts commit 8935485.
Fixing [flutter/flutter#27361](flutter/flutter#27361) and [flutter/flutter#27960](flutter/flutter#27960) Used static c function instead of category. The plugins effected are cloud_firestore firebase_admob firebase_auth firebase_core firebase_database firebase_dynamiclink firebase_mlvision firebase_storage google_signin camera
Fixing [flutter/flutter#27361](flutter/flutter#27361) and [flutter/flutter#27960](flutter/flutter#27960) Used static c function instead of category. The plugins effected are cloud_firestore firebase_admob firebase_auth firebase_core firebase_database firebase_dynamiclink firebase_mlvision firebase_storage google_signin camera
… nil on getFlutterError (#1274) When `getFlutterError` was introduced(#1226), some plugins started to throw exceptions for successful operations. This fixed the issue. Related issues include flutter/flutter#28344; flutter/flutter#28065; flutter/flutter#28103 It also fixed an unintentional typo introduced in the same PR.(#1226)
… nil on getFlutterError (flutter#1274) When `getFlutterError` was introduced(flutter#1226), some plugins started to throw exceptions for successful operations. This fixed the issue. Related issues include flutter/flutter#28344; flutter/flutter#28065; flutter/flutter#28103 It also fixed an unintentional typo introduced in the same PR.(flutter#1226)
… nil on getFlutterError (#1274) When `getFlutterError` was introduced(flutter/plugins#1226), some plugins started to throw exceptions for successful operations. This fixed the issue. Related issues include flutter/flutter#28344; flutter/flutter#28065; flutter/flutter#28103 It also fixed an unintentional typo introduced in the same PR.(flutter/plugins#1226)
… nil on getFlutterError (#1274) When `getFlutterError` was introduced(flutter/plugins#1226), some plugins started to throw exceptions for successful operations. This fixed the issue. Related issues include flutter/flutter#28344; flutter/flutter#28065; flutter/flutter#28103 It also fixed an unintentional typo introduced in the same PR.(flutter/plugins#1226)
Fixing [flutter/flutter#27361](flutter/flutter#27361) and [flutter/flutter#27960](flutter/flutter#27960) Used static c function instead of category. The plugins effected are cloud_firestore firebase_admob firebase_auth firebase_core firebase_database firebase_dynamiclink firebase_mlvision firebase_storage google_signin camera
Fixing [flutter/flutter#27361](flutter/flutter#27361) and [flutter/flutter#27960](flutter/flutter#27960) Used static c function instead of category. The plugins effected are cloud_firestore firebase_admob firebase_auth firebase_core firebase_database firebase_dynamiclink firebase_mlvision firebase_storage google_signin camera
Fixing flutter/flutter#27361 and flutter/flutter#27960
Used static c function instead of category.
The plugins effected are
cloud_firestore
firebase_admob
firebase_auth
firebase_core
firebase_database
firebase_dynamiclink
firebase_mlvision
firebase_storage
google_signin
camera