With the new android 13 there is now some new modifications regarding the permissions needed to receive notifications (arrgh!). Instead of buying all the time a new phone, I'm curious if there is a way to launch a simulator to test the new features? does someone know how I can run an emulator with android 13 so that I can try my app (made with delphi) if it's work well on android 13? I not necessary need to debugging feature, I only need to be able to install my app in it and run it. If possible I would like to avoid to install android studio
If I'm not totally mistaken, all last versions of suitable alternatives (Bluestacks, Genymotion, Xamarin Studio, ...) to Android Studio's emulator have release dates prior to the release date of Android 13.
So I fear you can't avoid Android Studio for now considering an Android 13 emulator, or you have to target a lower Android version if possible (as usually recommended).
And yes -- argh :-D Permission changes are always fun.
Related
anyone can help me with my android studio, so apparently I want to launch my emulators but it always counter same error. this are the things that I have done.
Firstly, I created a basic activity with java language and choose android 5.0(lollipop)
I have choose an pixel 3a(R) with API 30
I have downloaded android SDK also SDK tools which is Android SDK build-tools, Android emulator, Android SDK platform-Tools and also Intel x86 Emulator Accelerator
am I missing something?
this is the error message I constantly:
the error
Is there any solution so that I can launch my virtual phone without reinstalling the android studio back again?
I am really beginner so I hope that you can give the solution in a detailed step by step.
Good morning and thank you for your time,
I am maintaining a mobile App made in Xamarin classic IOS with the Visual Studio Mac IDE. Recently Apple told me that I had to increase the SDK of this application to 15 to be able to upload my new version to the App Store, for this I had to update the operating system to MacOS Monterey Version 12.3.1, to later update Xcode 13.4 and to update the SDK of my project, once this change was made in Visual Studio Mac debugging options were disabled and the debug icon was changed to compile. When I access Run in the top menu of visual studio mac, the options to start debugging are disabled and no matter how much I change the debug project options remains the same.
Regards
enter image description here
It is very likely that you have some other Debug configuration that works (in Xamarin it could be Debug|iPhone).
We recently acquired mobile solution that contains an ios and android project. Android project runs fine. When i run the ios project i get error stating
My environment is a windows laptop and a macbook pro running visual studio from windows.
I can pair to mac just fine
I am using automatic provisioning which appears to be correct since my team shows up in the team dropdown.
I feel like i did the provisioning correct because team would not show up in dropdown if not.
I have latest xcode installed on mac
I verified simulator runs fine on mac by starting through xcode
In the videos i watched as soon as mac was paired then more options appeared besides just simulator. (ipad, tvos, etc)
One question is when i registered my device i used the UUID from the macbook and not UUID of simulator. Could not get straight answer for this.
To be clear i am just trying to run the simulator and not a remote device.
Honestly i just want to be able to test the ios application. It should not be this many steps to just run a test. Is there a more simple way to test or am i on the right track?
Updating visual studio on my windows machine did the trick. I really wish the error would give me some kind of warning that would lead me to the conclusion that i needed to update visual studio. That would have saved me many hours.
I have a MonoGame application for iOS and I want to try it with the iPhone Simulator.
When I run the application from Visual Studio for Mac 2017 (I've also tried Visual Studio for Mac 2019... but the result is the same), the iPhone Simulator starts successfully but it doesn't run my application, i.e. it just shows the standard apps like calendar, mail, news, etc.
Any help would be really appreciated :-)
The problem was that my application was build as a 32-bit executable whereas the iPhone Simulator is a 64-bit application. Specifying the appropriate build options fixed the issue.
After having developed an app for a friend using Visual Studio 2013 Pro with the Apache Cordova Extension, I hoped to also get it runnning on an iPad 3 as fast as with Android. However, things proved to be more complicated than originally thought: The 99$ for an Apple developer account would be far too high for a single device development (the app is intended to only work on one device, no commercial intentions).
At least I now have the ability to use Mac OSX and XCode, which is connected to Visual Studio via network. Installing the app in the iOS simulator works as expected, but I'm struggling with deploying it on the iPad. I already considered jailbraking the device, as the warranty is yet expired and it wouldn't be a problem for my friend. According to the Information I found it would be possible; however, I could not find much about how to do that.
Thanks in advance.
After several months I finally found a working solution:
The latest XCode version (7 Beta 2) is able to sign iOS applications using an ordinary AppleID instead of a $100 developer license.
First, you will need to prepare the vs-mda-remote node plugin on your Mac and be able to build applications [See here how]. Using an appropriate deployment target in Visual Studio, the app can be tested within a virtualized iOS environment.
However, the deployment options Remote Device and Local Device will both fail when you haven't subscribed to the Apple Developer Program. Other methods (described here or here) requiring jailbreaking the device haven't worked for me either.
Interestingly, Apple seems to have changed their strategy not much time ago , finally allowing to sign and deploy apps on non-rooted iOS devices.
Whenever an app is built for the iOS simulator, vs-mda-remote will create a whole new build folder (named using a 3 - 5 digit random number) located in ~/remote-builds/builds. Inside that build folder, you will need to find and open the XCode project file with XCode 7 (example path: ~/remote-builds/builds/654/cordovaApp/platforms/ios/YOUR_PROJECT_NAME.codeproj).
After having connected and detected your iOS device, you should be able to select it as deployment target. Then you should follow these instructions, basically just adding an AppleID which should be used to sign the app. This wasn't possible with earlier XCode versions and is certainly much easier than using one of the "hack"-like techniques involving jailbreaking your device and practically voiding it's warranty.
Finally, you will only need to set the Code Signing Identity to the registered AppleID (for both the Project and the Target) and you're ready to deploy your app.
This method worked for me using iOS 8.3 and Mac OSX Yosemite 10.10.4.
If there are any other questions, please feel free to ask.
in Visual Studio 2015 Community RC, there is an option to debug the app developed by cordova in 'remote device' (iPhone or ipad) connected to the Mac osx. Pls. try it.