-
Notifications
You must be signed in to change notification settings - Fork 268
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
Not seeing the BlockAlertView on the iPad simulator #67
Comments
Is this related to the UIBarPositioningDelegate in IOS7? I've had to update several apps because of this. I had to make the view controller handle UIBarPositioningDelegate And add something like the following..
|
I don't think so. All I'm doing is this: |
@lpmacdevelopers I'm experiencing this exact same issue at the moment and I'm not running iOS 7 in the simulator. Have you figured out how to resolve the problem? |
@lpmacdevelopers You gave me a good pointer when you started referring images having a nil value. I have just fixed the problem for myself, have you added both of the following folders to your own project as per the following folder paths?
Make sure that "Copy Items to destination folder (If needed) is checked" as well as "Create groups for any added folders". The folder "To add to your projects" is deceiving as the images are also required. |
Hello,
I've been trying to resolve this issue with the BlockAlertView component, which doesn't display any text or render a background when invoked. All that is seen are two sets of three dots in the middle of the screen.
My investigations have revealed that in the "show" method, the background image is being set by using the format "alert--button.png" for the image file name, but the resultant image object has a nil value. I can confirm that the image resides in the file system and in the Resources sub folder. The Pods-resources.sh file also has this file with the correct path in the "install_resource" method call.
Any pointers in the right direction will surely be helpful.
Thanks
Ashley
The text was updated successfully, but these errors were encountered: