CODEWITHSUNDEEP
xcodefirebaseswiftuicocoapods
soonToBeDev
soonToBeDev

Reputation: 85

Installing Firebase to my Xcode project resulted into generating 4 warnings I cannot seem to find a fix for

I tried looking through many stackOverFlow posts in order to find the solution to this problem but I cant seem to find any, can someone explain why this error is generating and possible a fix to it? Thank you in advance!

Im working on this application in a course, and in this section of the module, I'm installing Firebase to the application in order to let a user register and login to the app, after the installing the the Firebase pods I ran into 10 errors, was able to fix 6 of them by doing some research but I was left with 4 errors that reflect back to the same line "typedef struct" in 3 different files, internal.h, credentials.h and ssl_security_connector.h.

/Users/adham/Desktop/Projects/Flash-Chat-iOS13/Pods/gRPC-Core/src/core/lib/security/credentials/credentials.h:205:15: Anonymous non-C-compatible type given name for linkage purposes by typedef declaration; add a tag name here

and it is highlighting this block of code

typedef struct {
  grpc_mdelem* md = nullptr;
  size_t size = 0;
} grpc_credentials_mdelem_array;

This error in gRPC-Core was also found in gRPC-C++ Group, it was labeled as "Semantic issue"

Im new to stackOverFlow please don't judge my posts, only getting started!

Upvotes: 8

Views: 3315

Answers (1)

Warren Burton
Warren Burton

Reputation: 17382

Do you mean warnings or errors ? By default those messages will be warnings.

You can switch off warnings from pod frameworks by adding

inhibit_all_warnings!

To your Podfile and calling pod install

If you want to fix the warning change the structure of that declaration to.

struct grpc_credentials_mdelem_array {
  grpc_mdelem* md = nullptr;
  size_t size = 0;
};

Lose the typedef and the name comes to the front after struct

But to make it sticky through pod installs you need to fork the repos and point to your own fork in the Podfile.

Most of the time unless it’s stopping your work you can ignore pod warnings.

Upvotes: 12

Related Questions