Google Authentication and Site Ownership Verification for Web App Development

I'm developing a Web app that requires Google authentication for users. I have followed the documentation at Google Shopping Content API Guide to set up authentication using my app's credentials.

Regarding project verification, the documentation mentions verifying site ownership using Google Site Verification. How do we handle this process if we have sub-domains?

Let's say I have a site example.com where I have the required home page, privacy policy, and terms of service pages. I have a sub-domain like dev.example.com that I want to use in the required URL fields. Is there any possible issue regarding this scenario?

Re John Hanley's comment:

Once you verify the naked domain (examle.com), the subdomains are automatically included. Additional verification of subdomains is not required.

Not always... I have two domains and two GWS accounts, one a subdomain of the other, like:

    blogs.org.uk
joe.blogs.org.uk

On each domain I have an alias domain:

       blogs.uk
   joe.blogs.uk

GWS recognises blogs.uk as verified but does not recognise joe.blogs.uk as verified and requires a separate TXT record code.

Go figure - doesn't make much sense to me.

(Though, your comment does give me some comfort I shouldn't worry about not having a verification code for joe.blogs.uk.)