Flutter_blue: [iOS]Cannot run in iOS app after adding flutter_blue

[Albinzr]

I have added flutter_blue to my yaml file after that I'm getting pod error

dependencies:
  flutter:
    sdk: flutter
  flutter_blue: "0.3.1"
  cupertino_icons: ^0.1.0

If I remove flutter_blue then it starts to work normally
Why is this issue happening and how can I solve this?

[pauldemarco]

Hi Albinzr,
What's the error message you're seeing?

If it's complaining about protoc, try performing Step 2 here: https://github.com/pauldemarco/flutter_blue/issues/40#issuecomment-371008826

[Albinzr]

@pauldemarco After I did the fix you said, I'm getting new set of errors

[pauldemarco]

Most of those are warnings but there is 1 error: flutter_blue/FlutterBluePlugin.h file not found...

Have you tried opening the project in xcode first?

[Albinzr]

I created a new project and added it, then it started working fine.

[pauldemarco]

Thanks for the report!

[truongsinh]

I have the same issue, and the culprit is this line
https://github.com/pauldemarco/flutter_blue/blob/ce43a748e949fa5b46fb97b0fac77d12d9238745/ios/flutter_blue.podspec#L21

Please be noticed that also in this line, the path will not work in Windows

[mateuszjablonski]

Is this ever going to be fixed? I have exactly the same issue, and it is over a whole year since it first occured.

[pauldemarco]

Multiple attempts have been made and reverted. There doesn’t seem to be
one that works for everyone. Leaving this open until there’s overwhelming
response, or until it’s addressed in an official flutter template.

On Fri, Sep 27, 2019 at 9:08 AM Mateusz Jabłoński [e-mail]
wrote:

Is this ever going to be fixed? I have exactly the same issue, and it is
over a whole year since it first occured.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pauldemarco/flutter_blue/issues/59?email_source=notifications&email_token=AD7TN5SUORYSXEADWDGNFGTQLYAVFA5CNFSM4EYM4B22YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7Y2XGY#issuecomment-535931803,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AD7TN5TMBWX6GYZJV6EEQR3QLYAVFANCNFSM4EYM4B2Q
.

>

Warm Regards,

Paul DeMarco
Embedded Systems Engineer
Buffalo PC Inc.
236 Pellman Pl.
West Seneca, NY 14218
Mobile: [phone]
Email: [email protected]

[mateuszjablonski]

I think I have managed to find a solution to the problem. It seems like setting headers as public solves the problem. Detailed info here. @Albinzr @truongsinh can you confirm that this solves the problem? @pauldemarco do you think that is the issue?

[KevinRohn]

I also have the same problem. Is there any update? Setting the headers as public works some times, but is not practicable for me, because i can't do this one codemagic.io which runs our builds. It is only possible on the local build machine.

[activeRobert]

Any update on this? Perhaps there is an older version that actually works?

[davidcv5]

Anything new? Having this with firebase make it even worse, can't find a way to make it build, changing the path affects all firebase packages.

[softmarshmallow]

Anything new? Having this with firebase make it even worse, can't find a way to make it build, changing the path affects all firebase packages.

+1 for firebase with fluuter_blue integration. something's badly chained

[jacobokoenig]

+1 also firebase with flutter_blue. It was working fine a while ago. Not sure what happened.