Native Text Fields Don't Allow Entry After Iad Called

Other
#1

Hi,

I did post about this on the old forum but don’t seem to be able to find it now.  

After calling an iAd, any native text boxes / fields will no longer allow input.  The reply in the old forum was that it was a known bug, just wondering if there is any news on it being fixed as my app relies on a search feature using the text field, but I am being restricted to one ad call per opening of the app (before textfield is created).  Which if a user just leaves it suspended means it could never call a 2nd ad.

Thanks

Gary

#2

Hi there,

I haven’t encountered this issue myself, since I’m not using native text boxes. but out of curiosity, does this issue occur both for iAds banners and interstitials, or just one or the other?

If it’s an issue just for interstitials, then a possible workaround would be to detect when the interstitial has been closed, and then delete and recreate your text box.

Of course, that might just be a stop-gap workaround – ideally the bug itself would have to be fixed.

  • Andrew
#3

Hi,

Im only using banners, so not sure about interstitials.  I did think about recreating the text box after each banner is called, but I have about 10 altogether for inputting information so isn’t that practical.  I was hoping it would be fixed soon, I have tried revmob now, but that also seems to have developed a bug where it won’t detect the device type.

#4

Hi there,

I’ve been trying RevMob as well without any problems – what issue are you referring to about it not detecting the device type?

  • Andrew
#5

hi,

when using the latest daily build, latest revmob sdk and iOS 6.1.3 on iPhone 5 ( not checked ipad yet ) I am getting the below error in xcode console

[RevMob] WARNING: device not identified, no registration or ad unit will work

I have used revmob before with no issues, so think I am implementing it correctly.  The only thing I have done different is use a build.settings which contains ios and android settings.  I’ll have another try tonight.

Thanks

#6

Interesting.  I suspect it’s because daily build 1063 changed the return value of system.getInfo(“deviceID”), which RevMob uses for device identification.  (That API changed because Apple is no longer permitting apps that access the device’s UDID.)

  • Andrew
#7

That was what I suspected.  I looked at the revmob.lua file and can see it does retrieve the device id.  Maybe I can try and sneak it out on build 1062 then before the 1st may.  Hopefully the revmob sdk will be updated and I can then update with the newer build.

Thanks

Gary

#8

That’s definitely a strategy.  :-)  Although I’ve heard that Apple is already rejecting some apps, even before May 1, that access UDID.

  • Andrew
#9

It is that whats causing the issue, I have just built with 1061 and works fine.  I’ll submit tonight and see how it goes.  thanks for the help.

Gary

#10

Hi there,

I haven’t encountered this issue myself, since I’m not using native text boxes. but out of curiosity, does this issue occur both for iAds banners and interstitials, or just one or the other?

If it’s an issue just for interstitials, then a possible workaround would be to detect when the interstitial has been closed, and then delete and recreate your text box.

Of course, that might just be a stop-gap workaround – ideally the bug itself would have to be fixed.

  • Andrew
#11

Hi,

Im only using banners, so not sure about interstitials.  I did think about recreating the text box after each banner is called, but I have about 10 altogether for inputting information so isn’t that practical.  I was hoping it would be fixed soon, I have tried revmob now, but that also seems to have developed a bug where it won’t detect the device type.

#12

Hi there,

I’ve been trying RevMob as well without any problems – what issue are you referring to about it not detecting the device type?

  • Andrew
#13

hi,

when using the latest daily build, latest revmob sdk and iOS 6.1.3 on iPhone 5 ( not checked ipad yet ) I am getting the below error in xcode console

[RevMob] WARNING: device not identified, no registration or ad unit will work

I have used revmob before with no issues, so think I am implementing it correctly.  The only thing I have done different is use a build.settings which contains ios and android settings.  I’ll have another try tonight.

Thanks

#14

Interesting.  I suspect it’s because daily build 1063 changed the return value of system.getInfo(“deviceID”), which RevMob uses for device identification.  (That API changed because Apple is no longer permitting apps that access the device’s UDID.)

  • Andrew
#15

That was what I suspected.  I looked at the revmob.lua file and can see it does retrieve the device id.  Maybe I can try and sneak it out on build 1062 then before the 1st may.  Hopefully the revmob sdk will be updated and I can then update with the newer build.

Thanks

Gary

#16

That’s definitely a strategy.  :-)  Although I’ve heard that Apple is already rejecting some apps, even before May 1, that access UDID.

  • Andrew
#17

It is that whats causing the issue, I have just built with 1061 and works fine.  I’ll submit tonight and see how it goes.  thanks for the help.

Gary