I was hoping that the Android version of the AR SDK was released since "The Rolling Dead" was released on Android.
Is it around for download now? What was used to create "The Rolling Dead"?
~Danilo
Currently the Sphero AR SDK only supports iOS, but we are working on Android.
https://github.com/orbotix/Sphero-AR-SDK
The SDK was added and then removed because it was unstable, the team no longer has time to update it.
Small discussion at the sphero forum:
http://community.gosphero.com/discussion/59/sphero-ar-sdk-for-android#latest
I'm interested in testing with Sphero AR for android as well and occasionally check in every few months or so to see if there's any new plans, thought I'd leave an updated answer :)
Related
I started using Xamarin.UITest for cross-platform testing (IOS & Android).
With Android it worked instantly without any problem and it keeps forking even after any SDK update or JDK.. name it!
But for iOS there was so many issue encountered with the device agent that didn't want to start, the wrong Xcode commande one, the wrong Xcode. Some time it worked, but out of no where it crashes.. then you must clean, rebuild, retry, cross your fingers it doesn't crash or at least that it will launch..
But now April 19 2019, I had an iOS update, combine with an Xcode update and sadly, it doesn't work anymore. I made a lot of research and attempt to recover my test case:
Downgrade Xcode to 10.1
Downgrade Xcode commande line tool to 10.1
downgraded the OS!
To finally rethink it. It's not a good solid testing tool if it breaks at every updates.
On the AppCenter it still works for both platform. But to create your test, you have to run them locally.. You can't anymore with iOS and if you find how to make it work, let me tell you : "See you for the next update!"
So the question is:
What are the alternative to do some automated UI test for iOS & Android using Xamarin?
Xamarin.UITest Xcode 10.2 support
Sorry to hear about your difficulty with the Xcode update.
Unfortunately Xcode minor updates for the last several releases have tended to break local iOS simulator testing, and occasionally device testing. I've seen this be an issue since at least as early as Xcode 9.x versions.
For context, Xcode 10.2 support was added in this package: https://www.nuget.org/packages/Xamarin.UITest/2.2.7.2002-dev
If you or future readers of this discussion still do end up using Xamarin.UITest, I recommend checking the release notes when new minor versions of Xcode come out to see if that support has been confirmed. Typically the support has been added in the 1st Xamarin.UITest package released after a new minor version of Xcode has been released.
(I generally haven't seen this issue with patch versions though, for example Xcode 10.2.1 didn't seem to cause any issues when it came out if it was run against a test suite that was working for Xcode 10.2)
Other testing frameworks
As for other testing frameworks, if you're using App Center itself; then Appium (JUnit) or Calabash are both able to be used with App Center Test and can be used cross-platform to run against your IPA/APK, generally regardless of what was used to write the apps in the first place, like Xamarin.UITest. (Though each framework has slightly different set up requirements and limitations.)
Outside of App Center Test, there may be other testing frameworks you can use; but that gets more into individual developer opinion which strictly speaking is out-of-scope for Stack Overflow answers.
Appium Studio which holds all the pros of native Appium. It also supports parallel execution with built-in test reporting mechanism. They also provide cloud devices with which you can check whether it is feasible for your project. Check out their documentation for more features.
Would the camera tracking functionality would of Google Tango Unity SDK become compatible to IOS?
Project Tango SDK are developed based on Android. I don't think it is compatible to ios.
also The SDK right now only works for Project Tango Device only.
other Android device also won't work
IOS is not going to happen, since this is native to Android. But to expand on your question, google is trying to make this into a mass market consumer product, but it's a really slow process. This is on of the most recent and helpful news stories I found on the topic
http://www.engadget.com/2015/05/29/google-qualcomm-project-tango-phone/
So I picked up my sphero today - it had been gathering dust for a year or so - thought I'd get back to writing some orbBasic stuff.
Visited their site and found this:
http://sdk.sphero.com/robot-languages/oval-oval-language/
But I can't find any information about how to stream the instructions end control the execution. Is this still work in progress? Maybe an accidental leak?
If it is available, that would be great. I can't seem to follow orbBasic stuff I'd written over a year ago. Not a fan of managing line numbers and figuring out what those variables hold.
Oval is a feature in Ollie and soon to be a feature in Sphero 2.0! Both the Android and iOS SDKs will be released on Github to support Oval at the same time as the firmware update enabling Oval.
Get the new Sphero SPRK app from the apple app store. It includes the firmware upgrade that enables Oval on Sphero 2.0.
Yesterday I've received a mail from the Apple Developer Center, stating:
Make sure your apps work seamlessly with the innovative technologies in iOS 7. Starting February 1, new apps and app updates submitted to the App Store must be built with Xcode 5 and iOS 7 SDK.
Will this mean the end of developing apps cross-device off of non-Apple devices?
It sure is a heavy restriction and I'm very disappointed with this news!
Could someone shine a light on this painful news?
I don't believe this is the case.
As long as the app is compiled using XCode, and using the iOS7 SDK, you should be fine.
When they say "built" they mean, it has a corresponding XCode project. Not that every line of code has been written in XCode. At least, that's my interpretation.
I am just starting iOS/iPhone development and I would like to start using XCode 4 instead of XCode 3.2. Is XCode 4 stable/feature complete enough for beginning iPhone development or should I stick with XCode 3.2?
I have run into far too many problems using beta versions of XCode, especially since you can't really have two versions of XCode one the same system. Apple already has a history of releasing things to developers before they are truly ready (just look at iAds for the iPad which were released months ago and have yet to deliver a single ad). So, if even Apple isn't ready to label XCode 4 as ready-to-go then you can rest assured its not really ready to go.
I recommend sticking with 3.2. That's what I'm doing until XCode 4 is officially supported.
Using XCode 4 calls everything you do into question. Having a problem with an API? Maybe it's XCode, maybe its your code, maybe its a bug in the API. You just don't know.
I would say no, it's not ready. I tried using it as my main development environment for about a week, and eventually switched back to 3.2. For one thing it crashed fairly regularly, but I could get passed that.
The big thing that caused me to switch back was a bug where the iOS simulator would think that certain resources existed in my app that didn't. Deleting the app from the simulator didn't work, cleaning the project didn't work, and deleting the derived data folder didn't work. Since it's not officially released, finding help for problems like this is a pain as well.
This is just one instance of the kind of problems you'll run into while using it, so I'd recommend avoiding it for now.
You can use Xcode 4 if you do not plan on using the current version (Preview 6) for submitting apps to the App Store.
iOS Dev Center:
Xcode 4 Developer Preview 6 includes
iOS SDK 4.2, bug fixes, and additional
features. To compile submissions for
the App Store, continue to use Xcode
3.2.5 and iOS SDK 4.2.