Incorrect nullability annotations in FlutterCodecs.h

Interface	Member	Current Signature	Correct Signature	Issue
`FlutterMethodCodec`	`encodeMethodCall:`	`- (NSData)encodeMethodCall:(FlutterMethodCall)methodCall;`	`- (NSData* _Nullable)encodeMethodCall:(FlutterMethodCall*)methodCall;`	Return type is implicitly `nonnull`, but encoding can fail and return `nil`.
`FlutterMethodCodec`	`decodeMethodCall:`	`- (FlutterMethodCall)decodeMethodCall:(NSData)methodCall;`	`- (FlutterMethodCall* _Nullable)decodeMethodCall:(NSData*)methodCall;`	Return type is implicitly `nonnull`, but decoding can fail and return `nil`.
`FlutterMethodCodec`	`encodeSuccessEnvelope:`	`- (NSData*)encodeSuccessEnvelope:(id _Nullable)result;`	`- (NSData* _Nullable)encodeSuccessEnvelope:(id _Nullable)result;`	Return type is implicitly `nonnull`, but encoding can fail and return `nil`.
`FlutterMethodCodec`	`encodeErrorEnvelope:`	`- (NSData)encodeErrorEnvelope:(FlutterError)error;`	`- (NSData* _Nullable)encodeErrorEnvelope:(FlutterError*)error;`	Return type is implicitly `nonnull`, but encoding can fail and return `nil`.
`FlutterStandardWriter`	`writeValue:`	`- (void)writeValue:(id)value;`	`- (void)writeValue:(id _Nullable)value;`	Parameter `value` is implicitly `nonnull`, but the writer explicitly supports `nil`.

The FlutterStandardWriter one is especially bad since it would prevent swift callers from passing in nil.

Navigation Menu