Per my comment above, the solution was to use the `@` sign in the `Name` column of GoDaddy, not the actual name of the domain that is owned.

To add a bit more information to this great solution for future reference.

DNS propagation can be monitored using a service like:
https://www.whatsmydns.net/
This will show you when your records are ready, thus can be verified by firebase.

As for subdomain, ie.
beta.example.com

The value would be &#39;beta&#39; instead of &#39;@&#39; or &#39;example.com&#39; for the godaddy DNS records.



TXT GoDaddy TTL time is approximately 2 hours, Please re-verify after  2 hour firebase.

I see you fixed your problem but for anyone trying to link their godaddy domain with the reset password/ verify email service in Firebase Auth you need to remove your domain name from the CNAME record name. 

Firebase gave me `firebase2._domainkey.mydomain.com` and in godaddy CNAME record name I only used `firebase2._domainkey` and it verified my domain.

In case you have to set up the acme-challenge for your https certificate you probably may get something like this:

_acme-challenge.domain.com

just remove domain.com

in the case, you might have a subdomain
_acme-challenge.subdomain.domain.com
change it only to
_acme-challenge.subdomain

it will work in a couple of hours


For **TXT** records use @ for host instead of mysite.com

and for

**A** record, if it is subdomain, just add subdomain in the place of host. for example, https://**subdomain**.mysite.com =&gt; just add &quot;**subdomain**&quot; in Host of your DNS records in godaddy.

I currently use `_document.js` to inject css into my Next.js app and I would like to start using `_app.js` to help inject data into pages. 

Was wondering if it possible to use _document and _app in tandem or should we only use one or the other?

Next.js use of _app.js and _document.js

I&#39;m using promises and have code that looks like the following:

    function getStuff() { 
      return fetchStuff().then(stuff =&gt; 
        process(stuff)
      ).catch(err =&gt; {
        console.error(err);
      });
    }

Or:

    async function getStuff() { 
      try {
        const stuff = await fetchStuff();
        return process(stuff);
      } catch (err) { 
        console.error(err);
      }
    }

I was doing this to avoid missing on errors but was told by a fellow user that I shouldn&#39;t be doing this and it is frowned upon.

 - What&#39;s wrong with `return ….catch(err =&gt; console.error(err))`?
 - I&#39;ve seen a lot of code that does this, why?
 - What should I do instead?




Why is `.catch(err =&gt; console.error(err))` discouraged?

I deployed my app and now I&#39;m trying to add my custom URL.  I followed Firebase&#39;s instructions and added their TXT record to my DNS (GoDaddy).  But now Firebase is saying it&#39;s still not verified.  I assume I&#39;m doing something wrong, but there&#39;s not much here to mess up...

[![Screen Shot of Firebase][1]][1] 


[![Screen shot of DNS][2]][2]


  [1]: https://i.stack.imgur.com/s8eST.png
  [2]: https://i.stack.imgur.com/exqvC.png

Firebase hosting not validating TXT record in GoDaddy

I deployed my app and now I'm trying to add my custom URL. I followed Firebase's instructions and added their TXT record to my DNS (GoDaddy). But now Firebase is saying it's still not verified. I assume I'm doing something wrong, but there's not much here to mess up...
<a href="https://i.stack.imgur.com/s8eST.png" target="_blank" rel="noopener noreferrer"><img src="https://i.stack.imgur.com/s8eST.png" alt="Screen Shot of Firebase"></a>
<a href="https://i.stack.imgur.com/exqvC.png" target="_blank" rel="noopener noreferrer"><img src="https://i.stack.imgur.com/exqvC.png" alt="Screen shot of DNS"></a>

Going through the docs, I encountered:

&gt; ...you can call functions directly with an HTTP request or a [call from the client][1].
&gt;  
&gt; ~ [source][2]

there _(link in the quote)_ is a mention about `functions.https.onCall`.


But in the tutorial [here][3], another function `functions.https.onRequest` is used, so which one should I use and why? What is the difference/similarity between them?

Documentation for `functions.https` is [here][4].


  [1]: https://firebase.google.com/docs/functions/callable
  [2]: https://firebase.google.com/docs/functions/#lifecycle_of_a_background_function
  [3]: https://firebase.google.com/docs/functions/get-started
  [4]: https://firebase.google.com/docs/reference/functions/functions.https#.onCall

Firebase Cloud Functions: Difference between onRequest and onCall

Hope all of you aware of this class, used to get notification token whenever firebase notification token got refreshed we get the refreshed token from this class, From following method.

    @Override
    public void onTokenRefresh() {
        // Get updated InstanceID token.
        String refreshedToken = FirebaseInstanceId.getInstance().getToken();
        Log.d(TAG, &quot;Refreshed token: &quot; + refreshedToken);
    }

To use this as i want to implement FCM, I extended MyClass from `FirebaseInstanceIdService`

But, Showing that **FirebaseInstanceIdService is deprecated**

Does anybody know this?,
What method or class i should use instead of this to get refreshed token as this is deprecated.

I&#39;m using : `implementation &#39;com.google.firebase:firebase-messaging:17.1.0&#39;`

I checked the document for same there is nothing mentioned about this. : [FCM SETUP DOCUMENT][1]

------------------------------------------------------------------------------

**UPDATE**

**This issue has been Fixed.**

As Google deprecated the `FirebaseInstanceService`,

I asked the question to find the way and i get to know that We can get the Token from **FirebaseMessagingService**,

As before, when i asked the Question Documents were not updated but Now Google docs updated so for more info, Refer this google doc : [FirebaseMessagingService][1]


**OLD From : FirebaseInstanceService  (Deprecated)** 

    @Override
    public void onTokenRefresh() {
        // Get updated InstanceID token.
        String refreshedToken = FirebaseInstanceId.getInstance().getToken();
        Log.d(TAG, &quot;Refreshed token: &quot; + refreshedToken);
    }


**NEW From : FirebaseMessagingService**

    @Override
    public void onNewToken(String s) {
        super.onNewToken(s);
        Log.d(&quot;NEW_TOKEN&quot;,s);
    }

Thanks.

  [1]: https://firebase.google.com/docs/reference/android/com/google/firebase/messaging/FirebaseMessagingService
  [1]: https://firebase.google.com/docs/cloud-messaging/android/client

FirebaseInstanceIdService is deprecated

I would like to know what would be the correct way to get Firebase token for sending push notification now that getToken() is deprecated.



What method should I use now since FirebaseInstanceId.getInstance().getToken() is deprecated

I&#39;m newbie to Firestore. Firestore docs says...

&gt; **Important**: Unlike &quot;push IDs&quot; in the Firebase Realtime Database, Cloud Firestore auto-generated IDs do not provide any automatic ordering. If you want to be able to order your documents by creation date, **you should store a timestamp as a field in the documents.**

Reference: https://firebase.google.com/docs/firestore/manage-data/add-data

So do I have to create key name as `timestamp` in document? Or `created` is suffice to fulfill above statement from Firestore documentation.

    {
    	&quot;created&quot;: 1534183990,
    	&quot;modified&quot;: 1534183990,
    	&quot;timestamp&quot;:1534183990
    }

Add timestamp in Firestore documents

I want to config Firebase Firestore. I followed all the steps, but at the last step, I got the error link below I mention.

After Executing this **pod install** command below error I got

&gt; [!] Automatically assigning platform `ios` with version `11.4` on
&gt; target `testing_gowtham` because no platform was specified. Please
&gt; specify a platform for this target in your Podfile. See
&gt; `https://guides.cocoapods.org/syntax/podfile.html#platform`.


My podfile:

    # Uncomment the next line to define a global platform for your project
    # platform :ios, &#39;9.0&#39;
    
    target &#39;testing_gowtham&#39; do
      # Comment the next line if you&#39;re not using Swift and don&#39;t want to use dynamic frameworks
      use_frameworks!
    
    
      # Pods for testing_gowtham
    
      target &#39;testing_gowthamTests&#39; do
        inherit! :search_paths
        # Pods for testing
      end
    
      target &#39;testing_gowthamUITests&#39; do
        inherit! :search_paths
        # Pods for testing
      end
    
        pod &#39;Firebase/Core&#39;
        pod &#39;Firebase/Firestore&#39;
    end

I saw this https://guides.cocoapods.org/syntax/podfile.html#platform but I did not find which line I need to change .

How to solve this issue?

Please specify a platform for this target in your Podfile?

    ping: google.com: Temporary failure in name resolution
This problem is what&#39;s happing when trying to ping a domain instead of a IP, at this moment in the resolve.conf it has the 127.0.0.57 IP, tried adding this

    nameserver 8.8.8.8

and it fixed the problem on the short term, im going to be running a daemon that need to contact my domain control panel. so I need a long term solution.
If anyone has a solution to this issue it could be awesome.

ping: google.com: Temporary failure in name resolution

So I am trying to get a **custom domain to work with my github pages** user site. I have followed pretty much the standard procedure for doing this as follows: (recommended by github here too: **https://help.github.com/articles/setting-up-an-apex-domain-and-www-subdomain/**). Note I need both the apex domain (example.com) and the www subdomain (www.example.com) to resolve to my github pages user site at username.github.io (the website itself is a **jekyll based blog** and I have checked that it compiles successfully before I started this process)

1. I added an **A record** to my DNS records at the registrar pointing to all of the four IP addresses provided by Github from the apex domain example.com: 
- 185.199.108.153
- 185.199.109.153
- 185.199.110.153
- 185.199.111.153 
2. Next I went in and added a **CNAME record for the www** sub domain pointing to username.github.io
3. And then I finally enabled the custom domain example.com under the settings tab of the repository (under Github Pages &gt; Custom Domain), and also enabled the **Enforce HTTPS** option after it was enabled within about an hour.

I have tried contacting my registrar and they said that everything in the DNS record seem fine and they get the following results: 

A records : 

 example.com.            21460  IN      A      185.199.111.153

 example.com.            21460  IN      A      185.199.109.153

 example.com.            21460  IN      A      185.199.110.153

 example.com.            21460  IN      A      185.199.108.153

CNAME : 

www.example.com.        7199    IN      CNAME  username.github.io.

As expected.

But I still get the following error in github (under the settings tab of the repository): 

&quot;**Domain does not resolve to the GitHub Pages server. For more information, see https://help.github.com/articles/setting-up-a-custom-domain-with-github-pages/.**&quot;

And when I try to access the site by typing either example.com or www.example.com, the browser redirects to https://example.com/ and I get the error (on Chrome):

**ERR_CONNECTION_REFUSED**
  
Note that there is a warning on the documentation by github saying:

**Warning: If your domain has HTTPS enforcement enabled, GitHub Pages&#39; servers will not automatically route redirects. You must configure www subdomain and root domain redirects with your domain registrar.**

I have no idea how to get around this. I suspect this is the possible cause of the issue. So a solution might be to circumvent this redirection, I just do not know how I would do this. 


How to fix: Domain does not resolve to the GitHub Pages server. Error in Github Pages for custom domain setup with Enforce HTTPS Enabled?

Today I deployed firebase hosting. After deployment, I noticed firebase creates file of `.firebase/hosting.ALPHANUM.cache`, where ALPHANUM is actually some random baseNN ish value.

### Question

* What is the purpose of this file?
* More especially, can I add this to `.gitignore`?
  * Or, I should not?

What&#39;s the purpose of .firebase/hosting. ALPHANUM.cache

I&#39;ve created Firebase Dynamic Links in other projects before using the page.link URL prefix (the only option at the time). However that no longer appears to be an option when enabling Dynamic Links for a new project today. It looks like the [docs for custom domains](https://firebase.google.com/docs/dynamic-links/custom-domains) were updated today. Unfortunately, while they provide some helpful examples, they don&#39;t explain how to resolve my issue in a way that I can understand.

[![error configuring dynamic links for custom domain][1]][1]

So this message seems to indicate that I need to &quot;Put links under a subpath&quot;. It seems to me that adding the `/link` path prefix here should accomplish that? But after making that change, I get the same error message.

&gt; It looks like you already have content served on this Hosting site. Put links under a subpath to avoid conflicts with existing content.

I order to try to work around this, I went to my project and added the suggested Hosting configuration and deployed it.

firebase.json:
```json
{
  &quot;hosting&quot;: {
    &quot;public&quot;: &quot;dist&quot;,
    &quot;ignore&quot;: [
      &quot;**/.*&quot;
    ],
    &quot;appAssociation&quot;: &quot;AUTO&quot;,
    &quot;rewrites&quot;: [
      {
        &quot;source&quot;: &quot;/link/**&quot;,
        &quot;dynamicLinks&quot;: true
      },
      {
        &quot;source&quot;: &quot;**&quot;,
        &quot;destination&quot;: &quot;/index.html&quot;
      }
    ]
  }
}
```
Even after waiting an hour, I keep getting the same error and I don&#39;t understand what to do.

Note that I have the rewrite to `/index.html` because I have an Angular Single Page Application hosted at www.devintent.com.

No matter what I do, I keep getting this error and the `Continue` button stays disabled. I tried using my naked domain devintent.com instead of www.devintent.com, but that didn&#39;t help. I tried using links.devintent.com, but got the same error. 

If I manually remove `disabled` from the `Continue` button, then I get this error message:

[![configure path prefix manually message][2]][2]
This links to the [docs for manually configuring hosting for dynamic links](https://firebase.google.com/docs/dynamic-links/custom-domains?authuser=0#manual) which has some steps that I&#39;ve already completed. Clicking the `Check Again` button just takes me back to the same error in the first image above.

---

Workaround to not use Custom Domains

I&#39;m happy at this time to use a `page.link` link, I just need to create a Dynamic Link and get unblocked on this task, but I can&#39;t figure out any way in the console to allow me to do that either.

Update on this: I figured out that I needed to add the subdomain to the `page.link` URL. The tooltip says &quot;or a free Google-provided domain (for example, yourapp.page.link)&quot; at the end. This is a little less prominent that I would have liked (as I didn&#39;t find it for quite a long time). Using `devintent.page.link` works for me as a workaround for now.

--- 

However, I&#39;m not sure why the Custom Domain configuration didn&#39;t work and why it would be the default if there are such complications with projects with existing Hosting configurations and custom domains.

  [1]: https://i.stack.imgur.com/VtNBJ.png
  [2]: https://i.stack.imgur.com/Cr34I.png

Content Type	Original Author	Original Content on Stackoverflow
Question	DoubleTri	View Question on Stackoverflow
Solution 1 - Firebase	JeremyW	View Answer on Stackoverflow
Solution 2 - Firebase	Alocus	View Answer on Stackoverflow
Solution 3 - Firebase	mekala goutham budda dev	View Answer on Stackoverflow
Solution 4 - Firebase	beowulf	View Answer on Stackoverflow
Solution 5 - Firebase	pedrommuller	View Answer on Stackoverflow
Solution 6 - Firebase	jkr	View Answer on Stackoverflow

Firebase hosting not validating TXT record in GoDaddy

Firebase Problem Overview

Firebase Solutions

Solution 1 - Firebase

Solution 2 - Firebase

Solution 3 - Firebase

Solution 4 - Firebase

Solution 5 - Firebase

Solution 6 - Firebase

Why is `.catch(err => console.error(err))` discouraged?

Next.js use of _app.js and _document.js

Attributions