As soon as I add a float or a double variable to my program, it stops working on BB models 8100 and 8800, both running OS 4.5.
I have a couple of newer phones with OS 5 and 6, respectively, and the same binary works just fine on those.
Why would this be?
Also, see "Float or double on Blackberry?" which led to this question.
When the application is started, before it really starts, it shows an error message to the effect of "modules bla blah can not verify blah". I'll update the message to the real one when I get a chance to start the broken app again.
Your quoted error message is still "modules bla blah can not verify blah", which is kind of vague, but it sounds like you are building against a SDK that is newer than BlackBerry OS 4.5, and then trying to deploy the app to a 4.5 device.
It's possible that float and double are the first references that pull in modules that don't exist on OS 4.5, so it appears to you that they are breaking your app, when it is really a build issue.
Related
I am testing a Xamarin Forms app on Android and iOS using Xamarin.UITest. Since the application depends on the GPS location, I need to set a fake location. I do this using
App.Device.SetLocation(latitude, longitude)
...where latitude and longitude are variables of type double which contain the desired coordinates.
This works fine on Android but fails on the iPhone Simulator with the following exception:
SetUp : Xamarin.UITest.XDB.Exceptions.DeviceAgentException : Unable to set location
ExitCode: 4
-d,--device-id <device-identifier> iOS Simulator GUID or 40-digit physical device ID
set-location <latitude,longitude>
Expected lat,lng: Got 48,135831,11,573423
I did some research and found a thread on the Xamarin Forums which says that it might help to round the fake coordinates to only 4 digits after the decimal point but it didn't help. Apart from that, I tried to hardcode the coordinates and to use floats instead of doubles but neither of the attempts worked.
What's going on there and how can it be fixed?
Here's my setup:
Xamarin.UITest version 2.2.4
iOS Simulator running iOS 9.3 on an iPhone 6
Host computer: Mac mini running MacOS High Sierra 10.13.6
The same issue occurred several months ago with the following setup:
Xamarin.UITest version 2.2.1
iOS Simulator running iOS 11.2 on an iPhone X
Host computer: Mac Mini running MacOS High Sierra (10.13.3)
At the time, I just left it alone, but now is the time where I need a fix.
Expected lat,lng: Got 48,135831,11,573423
It appears to be a bug in that Xamarin is using your local locale to convert those doubles to strings when they send them to simctl (and simctl is expecting decimal point-based strings or quoted decimals and thus it is parsing those are 4 separate numbers).
In your test code before setting the location, change the culture to en-US and set it back later to your actual culture if needed.
Something like this should work:
var currentCulture = CultureInfo.DefaultThreadCurrentCulture;
CultureInfo.DefaultThreadCurrentCulture = new System.Globalization.CultureInfo("en-US");"
// do some location setting / testing
CultureInfo.DefaultThreadCurrentCulture = currentCulture;
I am building an app using Delphi XE8 and FireMonkey.
I've got it working on Android and am trying to get it working on an iPad.
The iPad is running OS X 5.1.1.
I've got a Debug Provisioning profile.
First, when I tried to run the application on the iPad, I got the error message "Unable to install package. (e8000007)". According to Embarcadero's help page, this was because I was targetting higher versions. So I went to "Project -> Options -> Delphi Compiler -> Linking", found that the minimum target OS was 7.0, and set it to 5.1.1 instead.
Now I'm getting
Unable to launch process <ip address> using the parameters for the <profile name> profile.
The following error was returned: 'Unable to install package. (e8000067)'
This error code is not on the help page. I also don't find it when googling.
Since all these error codes start with "e", it's probably supposed to be a decimal number preceded by "e" for error. Searching for the hexadecimal equivalent of "8000067", i.e. "7A1243", only yields color codes.
I made a "Hello World" app, tried to run it on the iPad, and got the same problem.
What is Delphi error e8000067 ?
It seems that this happens when you're compiling/linking for a 64 bits device, when your device is 32 bits.
When I chose to compile/link for a 32 bit device, the error went away.
We are developing app for iOS and Android and we are using Ti.Gelocation to getCurrentPosition and then set the Region of the MapView of ti.map module.
The app is already on marketplace and downloaded, so we are developing an important upgrade with this new feature. We dont't have problem with Android platform, but with iOS version of the app we get a several error invoking Ti.Geolocation module
The error on iOS 9.x on iPad and iPhone (we have no test on iPod) is:
-[__NSCFString containsObject:] unrecognized selector sent to instance 0x1463d500 at GeoView.js (line xxxx)
This error happens with the project with it.vocami.vocamiapp app-id, in the test project (ap-id=it.vocami.vocamitest) that we use for research and test of new features, no error happens and all run good. When we add at every level of our code (in the first row too), for example, Ti.Geolocation.locationServiceEnabled, in the main vocamiapp project, we get the error.
We have tried all we could think but at the end, if we change the app-id, the code runs otherwise we get the error. We cannot change the app-id because we need to update our published app.
We are developing with AppceleratorStudio version 4.5.0.021602170281 and Ti SDK ver 5.2.0GA on Mac OS X 10.10.5.
I just recently was "hit" by the fact that when I made my app ready for Google Play I use a specific key/user to sign it with. That behaves differently from just running it locally on the phone.
I had to make sure that I had registered two certificates with Google's API in the developer console. It didn't give me exactly the message that you show - but wouldn't show the map with a location. And the way I read the location prior to showing it on the map led me in the wrong direction looking at permissions on Android first :-)
/John
I'm trying to diagnose my app with Address Sanitizer.
Although the app runs quite smoothly and I only wanted to get further checks regarding the memory alloc etc. I get the following error when I run the app.
It's my first time using Address Sanitizer but as far as I concerened it needs to point out to one of the developer's line of code.
It seems to me like it crashes at internal libary.
Any ideas or suggestions?
Apparently the problem was that I tried to run the game on an iPad with iOS8.0.
On iOS >= 9.0 it works fine.
Im not a "high level" programmer. I do not understand all this stuff really which is why I'm using phonegap instead of native programming. I'm doing nothing special. The "page" loads, there is an input box, you click it, keyboard pops up. Letters seem to work OK but as soon as you push a # or back space the whole app crashes with EXC_BAD_ACCESS.
This is in a 4.3 emulator. I do not have a device handy to try.
All the searching I've done are people talking about memory management and what not. I'm not doing any of that, nor would I have idea on how to.
Anyone know why this is happening?
Here is the offending line:
int retVal = UIApplicationMain(argc, argv, nil, #"AppDelegate");
Which is located insde Supporting Files > main.m > main()
^^-- I did not create that file. I'm not sure if phonegap created it or if it was created by xcode.
It turns out the problem WAS the fact that I was testing my code on a 4.3 SIMULATOR on an OSX LION virutal machine running on a win7 host.
I brought my code in to work the next day, hopped on one of the macs, installed xcode and ran the identical code on the simulator AND my coworkers iphone and the problem did not show up, at all!