It looks like I can't install WebWorks SDK 2.1 in Eclipse without having to build everything manually...screw that. I need to build my app for BB SDK 6, but I keep getting build errors on 6.0 API calls. I've set my default JRE to BB 6, but I seem to be getting facet errors.
The WebWorks Static Web Module doesn't want to play nice with everything else.
I'm I hosed on developing for BB6 or am I doing something wrong?!
Someone on the BB Dev forums mentioned the bbwp.properties file...apparently it has a property where you would specify the BB runtime or BB component pack. If this is the correct approach could someone provide an example of the setting?
Related
When deploying an existing Xamarin forms proj from Visual Studio I was getting errors like "Failed to load AOT module ‘System.Net.Http’ while running in aot-only mode". This had worked in the past, it seemed Xcode had recently updated before I hit the problem. I found I was able to get the project deploying by changing the csproj entry 10.0 to 10.3. It looks like I could change this setting and everyone would be ok if they also had updated xcode.
My concern is: Does this change what versions of iOS the application can support? Would it have any other surprises when deployed to the apple store?
One thing I don't understand is I am the only person seeing this issue. Another developer is able to deploy to an iOS device (iPad instead of an iPhone) that also has the latest version of iOS without problems. Running “xcodebuild -version” shows we have the same version of xcode installed (8.3.1) and running “xcodebuild -showsdks” shows we have the same iOS sdk available (iOS 10.3).
There is some good documentation on the iOS SDK version: https://developer.apple.com/library/content/documentation/DeveloperTools/Conceptual/cross_development/Overview/overview.html#//apple_ref/doc/uid/20002001-BABEBGCF
You can build against a higher version of the SDK and run against lower versions of iOS.
Building against different versions of the iOS SDK can cause differences in behavior, these may show as regressions in your application.
I've been scratching my head on this for a while. I need to build a LiveCode external for iOS 7, but the most recent LiveCode SDK (LiveCodeSDK-R14) only has support through iOS 6.0.
I've followed these instructions (http://livecode.com/developers/guides/externals/), and got to the point that I could see that the LiveCode scripts expect to be able to copy from an LiveCode folder that corresponds with iOS 7 which doesn't exist (RunRev/Components/LiveCodeSDK/components/5_5_3/device-7_0 and simulator-7_0).
I reinstalled iPhoneOS6.1.sdk and set my xcode project to build with this (had to follow these steps - Xcode 5 with iOS 6 SDK: 'UIAccelerometer' is unavailable: not available on OS X).
So, the external builds now. I get a .lcext file whose internals look like this:
M Filemode Length Date Time File
- ---------- -------- ----------- -------- --------------------------
-rw-r--r-- 68440 14-Dec-2013 14:55:08 iOS/External-Device-7_0
-rwxr-xr-x 19616 14-Dec-2013 14:58:00 iOS/External-Simulator-7_0
-rw-r--r-- 68440 14-Dec-2013 14:46:34 iOS/External-Device-6_1
-rwxr-xr-x 20040 14-Dec-2013 16:14:54 iOS/External-Simulator-6_1
- ---------- -------- ----------- -------- --------------------------
176536 4 files
It looks like I should have the libs to load the external on the device and simulator in either iOS 6.1 or 7.0.
Simulator
When I test in the simulator, the code after I call the external function doesn't run, so I assume it's erroring-out trying to load the external? Any way I can see what's happening here?
Device
When I build the stand-alone, I get this error -
performing iOS arvm v7 (or universal) device builds requires the iOS 7.0 SDK platform to be installed (available with XCode 5.0 or later)
But, according to XCode, I have the iOS 7.0 SDK installed.
Versions
Xcode Version 5.0.2 (5A3005)
LiveCode Community Edition 6.5.0 build 3009
Seems like I'm missing something - it shouldn't be this hard to load a simple library. Any suggestions?
You can put your code in a try/catch block to get the details of the error.
try
yourCommand
catch e
put e
end try
Put here does an NSLog so you can look for logs in Console for the simulator or Organizer for device. You will get mostly a list of numbers which you can decipher with this.
As for the error you are getting when building device builds it sounds to me like you might not have added Xcode 5 to your mobile support prefs in LiveCode.
I did a mobile application on java using Netbeans IDE.
It's working fine when I run in my system.
Problem is when I try to install it in my mobile its getting error like application error.
Can anyone help me find what went wrong?
I am using Sony mobile and in that it's getting "Application Error" nothing more then that, and even I try to install in another mobiles also it's getting like "error". I can't find what type of error it is.
You have to first check that APIs which you used in your application is supported in your phone or not. If APIs are not supported by your phone then it give error at installation time. And yes also check that your phone supported MIDP and CLDC version.
Ok it is very silly problem. When you create Java ME Application with Netbeans, by default it uses MIDP 2.1 Version. and I am sure your device supports MIDP 2.0 ( happened with me few times ). Just change your MIDP Version from 2.1 to 2.0 in NetBeans and then create .Jar file and try again, it will surely work.
We've upgraded to MonoTouch 4.0 and the new MonoDevelop.
In order to get .NET 4.0 , do we need to enable a setting, or does MonoTouch automatically compile against the newest Mono ?
Everything has been working perfectly, iTunes has accepted all our apps, all without issue. We've released now nearly 70 apps made with MonoTouch and have thousands of users.
MonoTouch 4 requires that you have previously installed Mono shared runtime 2.10.1 in order to install it.
Once you have installed Mono runtime, MonoDevelop and of course ios 4.3 sdk now you can install monotouch 4, once installed you are now able to get Net 4 love by creating a new iphone solution :) (yes you dont have to modify any settings)
Hope this helps
Alex
As far as I can tell from MonoTouch's website ( http://monotouch.net/Releases/MonoTouch_4/MonoTouch_4.0.0 ), it says "Core Mono Runtime upgraded to Mono 2.10" so it looks like dmcs ( http://www.mono-project.com/Release_Notes_Mono_2.10 ) is included. I don't have MonoDevelop installed, but I might be able to help you out with my suggestion:
Look in Project -> Options -> Build -> General -> Runtime Version (I couldn't post more than 2 links since I'm a new user.)
I hope this answers your question.
I have installed the Netbeans 6.7 IDE with Java ME included, but cannot create a Mobile Application project from the Java ME category. When I select the project type the wizard stops at "Finding Feature" with the message:
Not all requested modules can be enabled:
[StandardModule:org.netbeans.modules.mobility.end2end.kig jarFile:C:\Program Files\NetBeans 6.7\mobility8\modules\org-netbeans-modules-mobility-end2end-kit.jar.
I am attempting to run this on Vista Home Premium. I have tried to run the IDE as Administrator with no luck.
I am at a loss for where to go next as I cannot seem to find any information regarding this issue. Even if you don't have the solution any insight into this error message would be helpful.
I am unable so far to get the project running via the Netbeans IDE install. I have, for the time being, installed the Java ME SDK which includes a very stripped down version of the Netbeans IDE for mobile development.
I originally had some issues starting the SDK as well on Vista. The IDE reported that it could not connect to the device manager on localhost. After some searching I found this link: Java ME SDK Startup Problem which suggests changing the hosts file localhost entry from IPv6 to IPv4. The fix worked perfectly and I can now compile and run code in the emulator.
This is not an optimal solution as the SDK does not include the visual design tools, however I am able to get a basic project going in the mean time.
I have given up on the 6.7 version and have instead located and installed 6.5.1. This previous version has been working just fine and seems to do everything I need.
I ran into the exact same error today while installing NB 6.8 beta. To resolve it we need to install two plugins:
Java Web Applications (as mentioned by Ali above) and
Sun Java System Web Server 7.0
Note that these two are part of the Category called "Java Web and EE" hence the confusion that we need to install Glassfish App Server. But we need these two plugins because they are required for debugging using breakpoints in emulator. Netbeans runs a web server when we do breakpoint based debugging.
Also note that the Java Web applications needs SOAP Web Services and JavaScript Debugger plugins to run and so these plugins are also installed when you try to install it.
You also need to install "Java Web Applications" plugin.
Tools->Plugins->Available Plugins
If the module is present, you should try unzipping it to check its content makes sense.
You should also be able to rebuild it from Netbeans sources.
You can also try to figure out why this happens by debugging the module loader inside Netbeans from its sources, using another IDE, presumably the latest version of Netbeans you can find without the issue.
If the module is missing, you might want to get the missing jar file from an installation of a previous version of Netbeans, see if it is compatible.
6.5.1 isn't missing any module.
back in version 5.5, the mobility module had to be downloaded and installed separately from the main IDE.
If you want to consider using Eclipse for developing your J2ME app...I've written a post related to that some time ago: here.