farhan678 / adwhirl

Automatically exported from code.google.com/p/adwhirl
0 stars 0 forks source link

Opening a greystripe ad then coming back via home screen can lead to black screen #168

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Touch a greystripe app store ad.
2. After the app store displays, press the Home button.
3. Touch your app. It loads, and immediately goes to the app store again (bad).
4. After the app store displays, press the Home button.
5. Touch your app. It loads and displays a completely black screen except for 
the status bar (extra bad).

What is the expected output? What do you see instead?
- When you return to the app, nothing should happen except the app displaying 
normally. Instead it either activates the ad again, or turns the app into a 
black screen that stays until you terminate the app.

What version of the product are you using? On what operating system?
AdWhirl SDK 2.6.2, Greystripe SDK 3.1.1. On iPhone 4, 4.2.1.

Please provide any additional information below.
This problem is very intermittent and happens maybe 10% of the time, and 
perhaps not on all devices. I am not sure if it is possible to occur using the 
multitasking bar; I've only had it happen using the springboard.

I am not using full screen ads, but it seems possible that this discussion is 
related (black screen result):
http://groups.google.com/group/adwhirl-users/browse_thread/thread/7f33af7ce20557
93

Original issue reported on code.google.com by migra...@gmail.com on 11 Jan 2011 at 7:44

GoogleCodeExporter commented 9 years ago
This sounds like it might be more of a greystripe issue.  Have you been able to 
reproduce with the latest AdWhirl SDK and Greystripe library?

Original comment by wesgood...@google.com on 30 Nov 2011 at 9:07

GoogleCodeExporter commented 9 years ago
We just decided to not use greystripe.. no great loss =)

Original comment by migra...@gmail.com on 30 Nov 2011 at 9:37

GoogleCodeExporter commented 9 years ago
Thanks for the update!

Original comment by wesgood...@google.com on 2 Dec 2011 at 8:58