childbrowser not working ios6 phonegap 2.0 - xcode

I see the following problems using ChildBrowser plugin in ios phonegap.
My mapping file is updated with ChildBrowserCommand and I allowed external hosts to *
My Environment
Xcode 4.5
ios 6
Phonegap 2.0
2012-09-26 12:36:07.419 HelloWorld2[2566:c07] ERROR: Plugin 'ChildBrowserCommand' not found, or is not a CDVPlugin. Check your plugin mapping in Cordova.plist.
2012-09-26 12:36:07.420 HelloWorld2[2566:c07] FAILED pluginJSON = [null,"ChildBrowserCommand","
showWebPage",["http://google.com"]]

They released recently v2.1, I suggest you giving it a try since now they are supposed to officially support ChildBrowser plugin

Related

currently with Xcode12.3 Beta + iOS14.4Beta not supported to run

I am trying to run automation using Xcode 12.3Beta on iOS14.4Beta, but I am getting an error that says not supported. Any news on when apple will release Xcode12.4Beta or did anyone found a workaround for this issue?

How to change version of RoboVM compiler to 2.3.10-SNAPSHOT in Gluon Mobile

I have an issue with running my JavaFX/Gluon Mobile App on iPadOS 13.3 Actually the similar issue is described here: Gluon sample application failing on ios devices I've identify that the problem is caused by RoboVM and should be fixed in the version 2.3.10-SNAPSHOT
How can I change the version of RoboVM used by Gluon? In the Gluon documentation is mentioned the ios gradle extension property robovmVersion. This property can be set to the version robovmVersion ='2.3.5-ios12' but not 2.3.10. The reason is that on the bintray there is no version 2.3.10.
Is there any way to force Gluon Mobile to use RoboVM 2.3.10?
This is a temporary solution until the JavaFXPorts repository gets updated. There seems to be an issue with iOS 13.3 and JavaFX native libraries that's why apps crash even when using the latest 2.3.10-SNAPSHOT.
The breaking line of code was identified yesterday by Demyan Kimitsa who suggested to remove assert from the following native class
GlassApplication.m:635
assert(pthread_key_create(&GlassThreadDataKey, NULL) == 0);
becomes
thread_key_create(&GlassThreadDataKey, NULL) == 0;
I have created a build with the above change in native libraries and with the use of RoboVM 2.3.10-SNAPSHOT everything runs normal again even in the latest iOS.
Now that the issue is identified, I believe it is a matter of time until a new JavaFXPorts fix is published.
If you can't wait, you can download the HelloWorld sample with the new binaries from here. Adjust the parameters in build.gradle and you are ready to go.

ParseCrashReporting.framework is missing

I'm trying to add ParseCrashReporting in my app, but I can't find framework. According to the guide I had downloaded SDK (was trying both new and existing project for ObjC and Swift) but file ParseCrashReporting.framework just missed. Is it archive's error or incorrect description in guide? Where could I get latest ParseCrashReporting framework?
It's been deprecated and removed from latest sdk as announced in their newsletter. Check below issue for email message:
https://github.com/ParsePlatform/Parse-SDK-Android/issues/247

Error after updating to Xcode 7

I am developing mobile app with Ionic Framework and I just received very strange error that broke my whole build.
'myapp/Plugins/com.phonegap.plugins.facebookconnect/FacebookSDK.framework/FacebookSDK(FBLikeButtonBackgroundSelectedPNG.o)'
does not contain bitcode. You must rebuild it with bitcode enabled
(Xcode setting ENABLE_BITCODE), obtain an updated library from the
vendor, or disable bitcode for this target. for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see
invocation)
That happen after . It worked perfectly before upgrading to the new Xcode version 7.0. I have tried to disable the BITCODE for the project but the Facebook functionality of the APP does not work as expected.
EDIT
If I disable BITCODE for the project the Facebook plugin opens the browser instead of the app therefore Disabling BITCODE is not a solution in that case.
From Xcode 7, BitCode in enable it by default. You will get this error until all apps and frameworks in your bundle doesn't include bitcode.
to remove this warning you can disable this in Build Settings
Build Settings>All>Build Options>Enable Bitcode = NO
This is a known issue with the Facebook Plugin. There is an open ticket at https://github.com/Wizcorp/phonegap-facebook-plugin/issues/111614 - I'd suggest you keep an eye on.
As a work-around, you might try
Project > Build Settings > Build Options > Enable Bitcode = No
(found # http://forum.ionicframework.com/t/error-after-updating-to-xcode-7/32641)
I too face the same problem while updating the frameworks for giving iOS9 support.
1.To change In build settings:
Enable Bitcode = "NO"
Not only for your project targets, to set all of your targets including your pods(Project) targets.
2.Change the Build Architecure only:
Debug - YES
Relese - NO
That was fixed!
Here is what it worked for me:
I am stealing it from here :
https://github.com/Wizcorp/phonegap-facebook-plugin/issues/1116
Update the plist with steps 2 and 3 from e Facebook's iOS 9 guide
Turn off the bitcode setting (you already know how to do that :smile:)
You should update your Facebook SDK. It did the trick for me as the latest Facebook SDK version supports bitcode. You don't have to upgrade to v4 as version 3.24 works perfectly.
There are a few other steps for iOS 9 compatibility like whitelisting FB domains and authorizing FB apps.
The following version support bitcode and can compile with the flag set to YES:
Version 3.24
Version 4.x
The relevant section of the FB documentation says:
Is bitcode supported?
v4.6 and v3.24 of the SDK supports bitcode. If you are using earlier versions, you must disable bitcode.
All steps required to upgrade to iOS 9 (transport security / app whitelisting) can be found here:
https://developers.facebook.com/docs/ios/ios9
But I have to tell you that even though it compiles/link OK and uses an "integrated" Facebook login dialog, it still uses a browser as a modal view in your app. For me it is a regression from the previous Facebook app integration. I don't know whether there's a way to get the old "native" login dialog back.

Apple Match-O-Linker (Id) Error using CorePlot Framework

I'm migrating a project developed in Xcode6 for MacOSX from another MacBook where it was running just fine.
Here when I run my project I get all these errors:
as you can see the framework is correctly added
Now then I look for the error description and I found this:
all those errors are from methods used from CorePlot Framework
but the coreplot framework is already added on my project, what else do I need for make this work???
thanks for the supportmac

Resources