I am trying to change colour of top and status bars like so:
forge.topbar.setTint([255,0,0,50], function() {
console.log('Success!');
}, function(content) {
console.log(content);
});
but it spits out the error:
"-[ForgeApp statusBarBox]: unrecognized selector sent to instance 0x16638080"
I am using latest TopBar module Version: 2.2 and Toolkit version 2.0.1
It does not work on iOS7. Maybe this could be an issue?
I resolved this problem by upgrading the platform version to 2.0.3
It's marked as unstable however (2.0.1 is current stable) so YMMV.
I haven't had any crashes yet.
edit: I just saw proxim0 answered this in the comments an hour ago, too.
Related
I ran into this issue with Xcode 12.1 simulators running iOS 14.1. My code does compiles then I get the runtime error of
runtime/cgo: could not obtain pthread_keys
tried 0x118 0x119 0x11a 0x11b 0x11c 0x11d 0x11e 0x11f 0x120 0x121 0x122 0x123 0x124 0x125 0x126 0x127 0x128 0x129 0x12a 0x12b 0x12c 0x12d 0x12e 0x12f 0x130 0x131 0x132 0x133 0x134 0x135 0x136 0x137 0x138 0x139 0x13a 0x13b 0x13c 0x13d 0x13e 0x13f 0x140 0x141 0x142 0x143 0x144 0x145 0x146 0x147 0x148 0x149 0x14a 0x14b 0x14c 0x14d 0x14e 0x14f 0x150 0x151 0x152 0x153 0x154 0x155 0x156 0x157 0x158 0x159 0x15a 0x15b 0x15c 0x15d 0x15e 0x15f 0x160 0x161 0x162 0x163 0x164 0x165 0x166 0x167 0x168 0x169 0x16a 0x16b 0x16c 0x16d 0x16e 0x16f 0x170 0x171 0x172 0x173 0x174 0x175 0x176 0x177 0x178 0x179 0x17a 0x17b 0x17c 0x17d 0x17e 0x17f 0x180 0x181 0x182 0x183 0x184 0x185 0x186 0x187 0x188 0x189 0x18a 0x18b 0x18c 0x18d 0x18e 0x18f 0x190 0x191 0x192 0x193 0x194 0x195 0x196 0x197
The code runs fine on the iOS 13.5 simulators as well as on a physical device running iOS 14. I would like to have the simulators running and working. Does anyone have a solution for this issue to work on iOS 14 simulators? And if anyone might know if this issue would affect Apple Store submissions
I am assuming you are using a go library framework file with your iOS Project. We had a similar issue with our codebase. To answer your questions:
It won't affect Apple Store submissions/releases on the App Store - we have made few releases in the last few months and there have been no issues.
Regarding the issue itself, I assume this is because of the go version - you have not stated what go version you are using but this was prevalent if you were using an older version (1.10.x or previous).
Updating your go lib version to a newer release and building your framework file with that version should solve your problem
I haven't understood much on why the issue occurs but here's an answer that tries to explain something similar
I am facing issue with push notification.
Actually i want to make inline-reply with ionic version 3. we are using phonegap-plugin-push (https://github.com/phonegap/phonegap-plugin-push/blob/master/docs/PAYLOAD.md). in Android it will work perfectly fine. but in iOS it has not giving the example with inline-reply.
I have also see same functionality with native iOS and there it is working fine. we need to set some behaviour property in that. but i can not set those property while defining the categories.
Can you please check how to achieve this things in iOS ?
Let'me know if you need any further information ?
I have tried with phonegap-plugin-push.
I have already asked this question in ionic forum and created issue in phonegap-plugin-push gitHub repository. below are the link for your reference.
https://forum.ionicframework.com/t/can-we-do-quick-reply-or-inline-reply-in-ios-using-push-notification/125347/5
https://github.com/phonegap/phonegap-plugin-push/issues/2823
i think we need to set property in below configuration in ionic
const options: PushOptions = {
android: {
icon: 'icon_small',
clearNotifications: 'false',
forceShow: 'false',
},
ios: {
alert: 'true',
badge: true,
sound: 'false',
categories: {
reminder: {
yes: {
callback: 'confirmReminderCallback',
title: 'CONFIRM',
foreground: false,
destructive: false,
//some where over here need to set the behaviour property
},
no: {
callback: 'declineReminderCallback',
title: 'DECLINE',
foreground: false,
destructive: false
}
}
},
},
windows: {},
browser: {
pushServiceURL: 'http://push.api.phonegap.com/v1/push',
},
};
I used to use the userDistanceToManeuverLocation variable from the RouteStepProgress Class but this seems to just return nil recently.
Just in case I was doing something wrong I tried following the MapBox iOS nav tutorial (https://docs.mapbox.com/help/tutorials/ios-navigation-sdk/) but this had the same result.
Going by the MapBox tutorial I would do the following to get the variable:
let navigationViewController = NavigationViewController(for: directionsRoute!)
let distance = navigationViewController.navigationService.routeProgress.currentLegProgress.currentStepProgress.userDistanceToManeuverLocation
I don't seem to see any error messages or other concerns. I would get this variable on every tick of the users location but now just returns nil. Thanks for any help
So after some testing I figured out the issue is to do with the newer versions of MapBox Navigation (SDK MapboxNavigation). Anything from version 0.29.0 onwards causes issues. For now I'm sticking with version 0.28.0 and will have to report this to MapBox
Edit:
It looks like the latest version (MapboxNavigation 0.38.0 at the time of writing this edit) appears to provide a solution. I now use distanceRemaining found in the RouteProgress class which does the same thing.
I was using the previous version of PDFTron for iOS (6.5.4a). Now since a new version is available so I decided to upgrade to 6.7.2 . I am using static framework. Now when I open a pdf, go back from it and again try to open the same pdf the app crashes with the following error :
libc++abi.dylib: terminating with uncaught exception of type trn::Common::Exception: Exception:
Message: Bad image dimensions
Conditional expression: inout_size.x>0 && inout_size.y>0
Version : 6.7.1.53210N
Filename : PDFDraw.cpp
Function : CalcDevMtxFromSize
Linenumber : 239
There have been improvements to image reading, and this exception should no longer occur. Please update to the latest version. If the latest version doesn't help, then we would need access to the file in question.
I have recently updated to ReactNativeControllers 2.03 from 1.24. I have also updated RN to 0.25. I am using a fork which only adds a Podspec file. After sorting out all the import changes in RN I am now stumped on this error:
(See also https://github.com/wix/react-native-controllers/issues/59)
RCCManager.setRootController was called with 3 arguments, but expects
2.
If you haven't changed this method yourself, this usually means that
your versions of the native code and JavaScript code are out of sync.
Updating both should make this error go away.
The code in question:
In RCCManagerModule.m:
setRootController:(NSDictionary*)layout animationType:(NSString*)animationType globalProps:(NSDictionary*)globalProps)
and in index.js:
ControllerRegistry: {
registerController: function (appKey, getControllerFunc) {
_controllerRegistry[appKey] = getControllerFunc();
},
setRootController: function (appKey, animationType = 'none', passProps = {}) {
var controller = _controllerRegistry[appKey];
if (controller === undefined) return;
var layout = controller.render();
_validateDrawerProps(layout);
RCCManager.setRootController(layout, animationType, passProps);
}
},
As is evident, both have 3 parameters.
I've killed and restarted the packager. I've cleaned the Xcode project including derived data, and deleted watchman cache with watchman watch-del-all. I've deleted my node_modules folder, done npm install and pod install.
I've rebuilt the Xcode project. Still no luck. I don't know how to debug this further.
EDIT: I also tried to clean the pod cache, updated to Cocoapods 1.01...
I have a feeling there may be a red herring here somewhere. For reference my full trace looks like this:
2016-06-10 14:15:18.179 [warn][tid:com.facebook.React.JavaScript] Warning: ReactNative.Component is deprecated. Use React.Component from the "react" package instead.
2016-06-10 14:15:18.239 JustTuner[7523:185768] Launching Couchbase Lite...
2016-06-10 14:15:19.048 JustTuner[7523:185768] Couchbase Lite url = http://adamwilsonsMBP.lan:5984/
2016-06-10 14:15:19.050 JustTuner[7523:185768] Launching Couchbase Lite...
2016-06-10 14:15:19.058 JustTuner[7523:185768] Couchbase Lite url = http://adamwilsonsMBP.lan:5984/
2016-06-10 14:15:19.538 [error][tid:main][RCTModuleMethod.m:456] RCCManager.setRootController was called with 3 arguments, but expects 2. If you haven't changed this method yourself, this usually means that your versions of the native code and JavaScript code are out of sync. Updating both should make this error go away.
After spending many hours trying to work this out, I found that there was an out of date static library libReactNativeControllers.a in build/Products/Debug-iphonesimulator.
Deleting libReactNativeControllers.a and rebuilding the project solved the issue.
It seems that the Pod static libraries are now being saved in their respective folders e.g. build/Products/Debug-iphonesimulator/ReactNativeControllers/libReactNativeControllers.a
My guess is that the recent builds were saving the static lib in the subfolder, but the linker was picking up the out-of-date one. Anyone know why this might have changed recently?
Restarting metro with resetting cache worked for me:
react-native start --reset-cache
or
npm start -- --reset-cache
Try to Clean and Rebuild the solution in XCode if it happened in react-native iOS.