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

Error while testing Simulator and mac app #9

Closed
irshadpc opened this issue Dec 22, 2014 · 7 comments
Closed

Error while testing Simulator and mac app #9

irshadpc opened this issue Dec 22, 2014 · 7 comments

Comments

@irshadpc
Copy link

I got error when i was running both app and my display was stuck with some time and the both app did got error after my display blinking.After that the sample project crash with the below method

  • (void)readAndDiscardDataOfSize:(size_t)size overChannel:(dispatch_io_t)channel callback:(void(^)(NSError*, BOOL))callback .

Actually what you did with my systems.

@rsms
Copy link
Owner

rsms commented Dec 30, 2014

It's possible that you have some OS and/or hardware problems, unless you are able to reproduce it multiple times on a different computer.

@rsms rsms closed this as completed Dec 30, 2014
@irshadpc
Copy link
Author

I got the same error while am running the application

Sent from my iPhone

On 31-Dec-2014, at 1:36 am, Rasmus notifications@github.com wrote:

It's possible that you have some OS and/or hardware problems, unless you are able to reproduce it multiple times on a different computer.


Reply to this email directly or view it on GitHub.

@rsms
Copy link
Owner

rsms commented Dec 31, 2014

So you haven't replicated it on different hardware?

@irshadpc
Copy link
Author

irshadpc commented Jan 1, 2015

Yes,when I was testing my iPhone 5s it seems to be the same scenarios
On Thu, 1 Jan 2015 at 1:47 am Rasmus notifications@github.com wrote:

So you haven't replicated it on different hardware?


Reply to this email directly or view it on GitHub
#9 (comment).

@rsms
Copy link
Owner

rsms commented Jan 5, 2015

To reproduce with different hardware would be to do this:

  • Have two different Macs and two different iOS devices
  • Connect Mac A with iOS device A and get the same results
  • Connect Mac B with iOS device B and get the same results
  • Connect Mac B with iOS device A and get the same results

I'm assuming you found readAndDiscardDataOfSize to be at the top of the call stack on your Mac when thing crash for you. If this is on the iOS device then your reproduction on two different devices might be enough to prompt a lengthy debugging session.

@irshadpc
Copy link
Author

irshadpc commented Jan 5, 2015

Yah sure i will do this ,i need some time to do this.

On Mon, Jan 5, 2015 at 8:41 AM, Rasmus notifications@github.com wrote:

To reproduce with different hardware would be to do this:

  • Have two different Macs and two different iOS devices
  • Connect Mac A with iOS device A and get the same results
  • Connect Mac B with iOS device B and get the same results
  • Connect Mac B with iOS device A and get the same results

I'm assuming you found readAndDiscardDataOfSize to be at the top of the
call stack on your Mac when thing crash for you. If this is on the iOS
device
then your reproduction on two different devices might be enough
to prompt a lengthy debugging session.


Reply to this email directly or view it on GitHub
#9 (comment).

Thanks&
Regards.........

Irshad pc
09947187988
ichu501@gmail.com

@liyangv
Copy link

liyangv commented Jun 6, 2016

I met the same error while Duet is running in the background, turn off/uninstall Duet. problem solved,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants