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

Callout immediately disappearing #68

Open
bobspryn opened this issue Oct 3, 2014 · 7 comments
Open

Callout immediately disappearing #68

bobspryn opened this issue Oct 3, 2014 · 7 comments

Comments

@bobspryn
Copy link

bobspryn commented Oct 3, 2014

Not sure what code is causing it, but my callout immediately disappears when presented. Rolled back to 2.0 and it works as expected.
¯_(ツ)_/¯

http://www.screencast.com/t/ssGLa1dIS

I'll dig in if I get the time.

@nfarina
Copy link
Owner

nfarina commented Oct 3, 2014

Hm that is weird ... if you can post some code that reproduces it in the sample project that would be helpful!

@muccy
Copy link

muccy commented Nov 27, 2014

I confirm this issue. I have no time now to investigate further. I can only say that dismissCalloutAnimated: is not called, but callout disappears. I also placed a breakpoint in animationWithType:presenting: to see if strange animations are fired: nothing.
I'm using your library with MapKit. Downgrading to 2.0.0 is a workaround.

@briomusic
Copy link

I can also confirm this issue, it seems to have been introduced between 2.0.0 (working) and 2.0.2 (not working).

As I am trying to get the project to work with 2.0.0 I noticed that self.calloutView.contentViewInset is not yet supported. How can I determine the frame of the calloutview in this version (2.0.0)? Currently I have a massive white border around the calloutview as I would like to have it.

(I am aware this was fixed in 2.1, but is there a workaround that people used to use in 2.0.0?)

@nfarina
Copy link
Owner

nfarina commented Jul 23, 2015

Is this happening in the sample project with MKMapView?

@briomusic
Copy link

haven't had the time to check as we are on a deadline project. my new workaround is to use the current version and present-and-dismiss a blank callout just to clear the pipes :) once this beast is in the app store I am up for investigating the causes, but right now I am going to have to leave it at that. the strange thing is that the callout and all its subviews are visible in Reveal.app - just not on device/simulator.

@nfarina
Copy link
Owner

nfarina commented Jul 29, 2015

OK well if anyone can repro in the Samples app at some point that would be most helpful!

@adamcohenrose
Copy link
Contributor

Could be the same issue I just fixed in #99 ?

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

5 participants