Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

device.getInfo().isVirtual not true in iOS Simulator #720

Closed
chrisspiegl opened this issue Dec 4, 2021 · 3 comments · Fixed by #726
Closed

device.getInfo().isVirtual not true in iOS Simulator #720

chrisspiegl opened this issue Dec 4, 2021 · 3 comments · Fixed by #726

Comments

@chrisspiegl
Copy link

chrisspiegl commented Dec 4, 2021

Bug Report

Plugin(s)

  • @capacitor/device

Capacitor Version

  • capacitor cli 3.3 .2
  • core 3.3.2

Platform(s)

macOS / iOS

Current Behavior

Trying to get if the app is running in the simulator or on real device with:

const dev = await Device.getInfo()
const runningInSimulator= dev.isVirtual

But for some reason in the simulator it tells me that dev.isVirtual is false

I also tried if it shows the other info and it does.

Expected Behavior

isVirtual should be true when running in iOS Simulator

@jcesarmobile
Copy link
Member

I can't reproduce in our test app.
Which simulator did you choose?
are you on M1 mac?
is the platform value correct?

@chrisspiegl
Copy link
Author

Hi, I will get more info and an output of all the info values.
But as a quick reply, yes, I am on a M1Max machine.

@ionitron-bot
Copy link

ionitron-bot bot commented Sep 30, 2022

Thanks for the issue! This issue is being locked to prevent comments that are not relevant to the original issue. If this is still an issue with the latest version of the plugin, please create a new issue and ensure the template is fully filled out.

@ionitron-bot ionitron-bot bot locked and limited conversation to collaborators Sep 30, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants