I just implemented admob ads in my iOS app.
The admob site says this:
Your pages are displaying blank ad units because you haven't yet
verified your PIN
Indeed, I haven't verified my PIN yet.
However, looking at my app, when I am not in test mode, I am receiving legit ads.
So, do I need or not the PIN verification? Why am I getting (apparently) legit ads?
ADMOB technically doesn't work on any device without a validated pin because you won't get paid.
It doesn't cost anything to get a pin but the wait can be compared to waiting on a shipment of LED's and bezels from Szechuan China which takes about a month.
Click here to get an ADMOB PIN
There is a lot of noise over here for the same issue. I think you can read through these links, if not yet done.
Google Product Forum
LInk here also
May be that, you get a solution there.
my site has a Smart app banner deployed, but i am not certain if it shows up every single time a visitor goes to the page. does it always render? if not, how often? what are the particulars here?
I created a router that connects to facebook to get some info before a user may access the internet.
First they connect, get the Captive Portal Page and then continue to a facebook login. Since the upgrade to iOS7 it fails to load the facebook login page. On my mac with the Captive Portal Assistant it has no problems and even on the phone itself while using the iOS version of safari there are no problems.
What is going wrong here? Is facebook filtering request from the iOS7 Captive Portal Assistant or is Apple doing some sneaky stuff here?
It seems the problem is widespread and only related to facebook.
Update: I worked with the beta's and they worked fine a few weeks ago. Now with the same beta version it doesn't anymore. So another point for the facebook explaination.
Regards, Cas
This problem was fixed by Apple since IOS 8. But as all iPhone 4 users can't upgrade to IOS 8 this problem is still one.
The IOS 7 devices check for the following domains:
www.appleiphonecell.com
captive.apple.com
captive.apple.com
www.apple.com
www.itools.info
www.ibook.info
www.airport.us
www.thinkdifferent.us
Whitelisting this domains stops the login mask to be appearing as the IOS device thinks, that the internet is working as expected. This way you have control on the things which happens, as the IOS device does not interrupts anything, if you use a normal browser for login.
If you don't whitelist the domains, the following thing happens. I debugged it on routers with several IOS devices and they all did mostly the same:
If you connect to a wifi, the IOS device tries to connect to one of the domains, which are listed above. If it can contact one of the domains, it tries another one. If it can't, it starts the redirect, which is controlled by the router. Sometimes it query one or more domains, before it thinks, that the internet is working.
After the check, the login screen redirects to your router and then to the login screen of your captive portal. This behavior stayed the same as it was on IOS 6 or before.
Now you start an oauth login to a 3rd party provider like Facebook, Google or Twitter. And now the difference appears. You can check it on a router, if you run it in debug mode. As the IOS device goes to an other domain for oauth login (like www.facebook.com) the iPhone thinks, that something changed and starts to query one of the apple domains, which are listed above. The user sees only a white screen and in the background the IOS device tries to contact one of the domains repeatedly. For the user this seems to be an error, as the screen stays white or takes very long to show the login on the 3rd party provider. Sometimes it stops loading and nothing happens forever.
To avoid this behavior, you must whitelist the above listed domains. This is a not a common behavior for IOS users, but this way, your browser have the control of the login session and the IOS device don't interrupt it as it does with the login screen.
Some shallow parts of information is reported on the following sites:
https://supportforums.cisco.com/docs/DOC-36523
http://www.cadincweb.com/why-your-apple-ios-7-device-wont-connect-to-the-wifi-network
https://discussions.apple.com/thread/5355766
I couldn't find a detailed description of the problem and found the one above myself by debugging all parts with some routers and IOS devices like iPhones and iPads.
I've just tested various router settings and noticed that iOS 7 is NOT trying to contact above mentioned sites/URLs when router's DOMAIN field is blank.
My guess is that blank domain points to a consumer-type network set up and Apple is not expecting a Captive Portal at such network. If you have access to administer your router see if you can clear out the DOMAIN field (and restart/retest).
I found my solution to my problem. (a while ago, but I found this post again)
First I found out, iOS makes 3 calls, first to check, second to get the page that needs to be displayed, third to check again after the pageload. Then I discovered, for every POST or GET action made by the page, regarding of the source page was refreshed, iOS checks for an active internet connection. Since the facebook api makes a lot of calls, the browser starts stalling(possible in combination with QoS on my router) and freezes the page.
My Solution:
Since I am in control of the DNS records of the Router I use, I redirected all domains towards my own server.
First I saved the check request, this to later identify the user when he comes back for the 3th request.
When the second request comes I just display an info window that every thing is right, and the user has to click the "Done" button.
The page is loaded, so iOS checks again, but i recognize the user so I display the OK-code Apple also displays. The "Done" button us show, and the user has "internet", according to iOS..
On the page that I display, I instruct the user to open the webbrowser. When he does, he opens a page and my portal with the right page is shown(I can detect this based on the Browser Agent). Then my facebook api start doing its job, and of we go :-)
Let me know if someone needs some more info on how to detect or maybe even a code sample if necessary.
Extra Information
To capture a user on your own server, redirect every request to your processing page using for example .htaccess. The request is made to a domain with a subfile e.g:
http://captive.apple.com/getrT09Nx7G/YNrnUOulnDj/3cfrq3M40iR.html
To keep multiple users apart, use the unique url the device tries to contact when checking for internet, in this case: /getYT09Nx7G/YN1nUOulnDj/3cfMq3M40iR.html
I am testing a website on an Ipad. It seems that if someone clicks on an email link, an email program will open in full screen (taking the user away from the browser). What makes it annoying is, there is no "close or X" button for them to leave the mail program. How do my ipad Visitors go back to the browser?
Is there a way (or a HTML code) where if someone click on an email link on an Ipad, it will open up the email program in a small window without taking the visitors away from the brower?
iOS's UI is based on the concept of full-screen apps. To return to the browser, your user must return to the browser app. This can be done using the button, or (if configured) some multi-touch gestures (I use a 4-finger swipe to the side, but I can't remember what the default is).
You should not be trying to change the user interface of a specific device from your website. You might help a few users who have not yet got used to their iOS interface, but you will confuse and/or annoy all the ones who have.
If I wrote to you and asked for help because everyone else in the whole continent was driving on the wrong side of the road, would you try to fix the entire road system? No! I hope you'd just tell me how (or not) to drive. Same deal with the existing UI on any device — let your user learn to use it properly.
I am working with a 3rd party web service to process credit card payments.
When I swipe a credit card via google chrome the payment is detected and processed.
However when I attempt to swipe a credit card via the built in Delphi web browser TChromium, nothing happens.
Can't figure out why its not working are their any settings I need to set on the TChromium browser?
Update
I have verified that that the card reader reads and posts the data to whatever field/component is selected.
One difference I have found with Chrome and the TChromium web browser is that when I process a card in the TChromium web browser it automatically tabs to the next html component after processing the card.. Where this does not happen in Chrome it just stays with the current field/component selected.
The Question title is misleading but only because I did not understand what was happening after some investigation I was able to solve the problem. I hope this answer might come in Handy for someone someday though its a pretty isolated problem.
So I found that the MagTek reader reads the credit card data to the field and then Sends a "Enter" button afterwards.
And the Program I am currently working with has an option where when a Enter Key is pushed it will instead send a Tab so that a user can get to the next fields by the enter key.
So the program was intercepting the MagTek reader initiated enter key and replacing it with a tab which interfered with the payment process.