You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like if people are using multiple adwhirl spots within one application
it will cause some issue with the appid and send (null) instead. The same thing
happened for android and I think I fixed it - so I think these are coming from
the iPhone version
I'm seeing a decent amount of these in the logs:
GET
/exmet.php?appid=(null)&nid=26fe866b88e74d6ba5d1be984151c978&type=1&uuid=2B8DEFE
ADAC20ADAFFF6647813794E22&country_code=en_US&appver=223&client=1 HTTP/1.1
Original issue reported on code.google.com by jpin...@google.com on 22 Jun 2010 at 9:45
The text was updated successfully, but these errors were encountered:
For the appid, the AdWhirlView simply calls the delegate's
adWhirlApplicationKey method. The only way I can think of that it can be null
is when the delegate method return nil. The AdWhirl code is very simple and I
can't think of any situation, multiple adwhirl spots or not, that can cause the
appid to be nil other than that the app delegate returns nil for
adWhirlApplicationKey. In which case, it's the delegates responsibility to
return a proper appid. So for this it doesn't seem like there's anything for us
to fix.
Original comment by nigelc...@google.com on 13 Jul 2010 at 7:16
Original issue reported on code.google.com by
jpin...@google.com
on 22 Jun 2010 at 9:45The text was updated successfully, but these errors were encountered: