I spent a couple hours thinking I was writing a “react native” app but it turned out I was actually tricked into writing an app for the “expo” platform which can’t be turned into a “react native” app or used with non-“expo platform” apis without significant changes, cool, thanks.
(in the half hour since this tweet I tried to get the app running on an iOS simulator and had no luck whatsoever and now once again I am defeated and I suspect this iOS project will go the way of all my fucking iOS projects)
the worst part of this is I can’t actually ask anyone how to fix this because everyone would tell me I’m a giant moron for not knowing how to set Xcode to look in a framework I dragged into it for headers :^)
@cat <AppAuth/AppAuth.h>
@eurasierboy yes, unfortunately that’s not what the instructions say <_> so I’ve opened a ticket
@cat ahh yeah I see they want you to mess with header search paths... 3: you try the cocoapod approach? I try to stay away from managing static libraries if I can
@cat on another note this library looks a lot better than the one I’ve been using >.> hope they can help ya out!
@eurasierboy I did this with Carapace or whatever the other one is called. Maybe I should try cocoa pods instead.
I’ve been doing software dev for like a decade
I still don’t know how to tell XCode where the fuck that .m file it’s complaining about is