I'm trying to add FirebasePerformance to my app. For adding monitoring for specific network requests I used the example from here: https://firebase.google.com/docs/perf-mon/get-started-ios
However, I get "Unresolved identifier 'HTTPMetric' ". I do have imports for Firebase & FirebasePerformance in my .swift class.
If anyone had the same issue I would really appreciate some help.
Apparently, running pod update fixes this. I got my answer here:
https://github.com/firebase/firebase-ios-sdk/issues/1071
Related
I am getting error on ios while executing function GoogleSignin.signIn() of react-native-community/google-signin
Any suggestion or help will be highly appreciated, Details and repo for reproducing the issue you can find here.
https://github.com/react-native-community/google-signin/issues/828
At last, I found the problem with react-native-google-signin the problem was with my previous configurations where i was trying to use google sdk and framework and my project was still using these files instead of using newer version and coco pods,
Have a look at this how i solved this issue.
I'm pretty new to forum and I really appreciate the passion that all of you use to solve the questions.
So I'm here because I'm struggling to integrate the GoogleWebRTC in my Xamarin Form project in the iOS part (I'm been able to make a native objC test app ), I've try to integrate it via CocoaPods with Sharpie Pod and bind it, but I'm not be able to resolve all the errors created in the bind on ApiDefinitions.cs.
After some time I found this project https://github.com/valentingrigorean/apprtc-ios-xamarin that has successfully bind the library and after some bug fix
( editing WebRTCBinding.csproj and remove the -lstdc++.6 linker and removed some errors in code)
but when I try to add that binding library into my project and try to run return me :
Objective-C exception thrown. Name: NSInvalidArgumentException Reason: +[RTCPeerConnectionFactory initializeSSL]: unrecognized selector.
What am I doing wrong?
Thanks in advance.
I was also looking for a solution and spent a lot of time to get it running.
What I did and what helped me with the project you mentioned
- add both projects WebRTC and AppRTC into your project
- link from your project to this both projects
- Deleted lstdc++.6 as you did already
- Add both delegate IARDAppClientDelegate, IRTCEAGLVideoViewDelegate into the class where you want to use it. You can add "RTCPeerConnectionFactory.InitializeSSL();" as test into for example ViewDidLoad and compile it for simulator and device.
Does it work or do you still get erros?
I installed FirebaseDatabaseUI via Cocoapods, closed the .xcodeproj then opened the .xcodeworkspace, but whenever I try to import it within my code, it keeps saying No such module 'FirebaseDatabaseUI'
Supposing it might be a dependency issue, I decided to install the FirebaseUI full bundle by pod 'FirebaseUI', but achieved no success at all. As can be seen in the screenshot I took of my code, FirebaseDatabaseUI is the only FirebaseUI library in which is occurring the issue.
Can someone tell me what might be wrong?
Actually, all subspec like Database, Firestore, Auth... is implicitly belong to FirebaseUI. You saw only FirebaseDatabaseUI get error warning because you put it in the first place, if you put other FirebaseXYZUI to the first place, it will also display that error.
To fix the error, simply import FirebaseUI and remove all other FirebaseXYZUI.
Hope this helps.
I'm trying to get a reference to my app delegate from a UIViewController but I keep getting an this error message:
'sharedApplication()' is unavailable: Use view controller based solutions where appropriate instead.
I've been reading all the articles dealing with this kind of message but my problem seems unrelated as I'm not using any third party framework. While a Today Extension is part of my app, the class in which the error occurs is totally unrelated. I even created a completely new class and keep getting the same error:
When I do the same thing in a playground it works fine. What am I missing?
Problem solved. I've been to the Build Settings of my app again and stumbled over
Require Only AppExtension-Safe API
all set to YES. The default though is NO. When I set this to NO the error disappeared.
I sure don't remember ever touching or even knowing about this but luckily now it works.
I ran into the same error when I created and added a new target to my project (a Remote Service Notification target) and added the target definition incorrectly in my podfile.
I was following directions from a third party notification platform and they were unclear as to where to place the target definition. Initially, I added the target definition within my main target, much like the Tests target definition. This mistake led me to this error.
I ended up moving the remote service notification target definition outside of my main target to the bottom of my podfile and that resolved my problem.
In case anyone came through this error after 3 years from the question time.
Make sure that the swift file target Membership doesn't include a Today Extension.
In my case, I have not defined import Foundation in the file causing the error.
silly and late but could help an absent-minded like me. Cheers.
Hello fellow stackers I know this question has been asked before but all of the answers I have seen have not worked for me. I keep getting the following error: No such module 'CloudKit'. I only get this error for the watchkit extension interfaceController the iOS project has zero issues and this whole problem started happening when watchOS 2 came out.
Things I have tried:
changing the framework path to $(SRCROOT)
changing the framework path to ${TARGET_BUILD_DIR}/CloudKit.framework
I tried placing the CloudKit.framework file directly into my project folder which actually gets rid of the no such module error but then I get the “_OBJC_CLASS_$_viewsampleViewController” error
Please help me. Any suggestions would be appreciated:)
Apparently WatchOS 2 decided to drop CloudKit technologies which is a big downer. Now if you wanted to use CloudKit for the watch, you need to relay the data from the parent app which is also a huge buzz kill. I found this in the documentation here: https://developer.apple.com/library/watchos/documentation/General/Conceptual/AppleWatch2TransitionGuide/index.html