Micro-Pocketbook
Simply Generational!
ColorCoverProfile
HOST FOR : BUSINESSES   |   EVENTS   &   PERSONALITIES 
Are you wondering where you could host more information about your business, event or simply looking for a place to have your valuable information preserved or items documented??? 

Look no further than Infocode a platform dedicated to host and share more information than what your prints can hold making it accessible with the power of QR-codes & Links ensuring that every inquiry is met with clarity and professionalism.

Create unlimited content domains and get associated scannable QR-codes or Links to embed on your marketing material, digital designs or products and utility items.


 

Wheather you have an Information Website or not
WE'VE GOT PLENTY OF SPACE FOR YOU TO HOST YOUR INFO




 


HOW IT WORKS


CREATE A PERSONALIZED DOMAIN : 
★ Create & Personalize your new information domain by adding a custom password and filling required profile/contact details.



DRAFT, SAVE & VALIDATE : 
★ Create screens with customised content to comprehensively convey your information with a more personalized touch and always validate to ensure your audience is consuming accurate and updated information.



COMPLETE PAYMENT : 
★ Complete your subscription with a payment plan suitable for your needs with your prefered payment option to unlock public accessibility and availability.



PRINT / SHARE QR-CODE & LINK : 
★ Share your hosted information to your audience anytime through QR codes & Links associated to your domain - embedding them on your marketing materials, print media and digital designs.




OUR CORE SERVICES





HOSTING SPACE : We offer you unmatched safe physical storage space to host your content and files on our cloud service making them publicly accessible to your audience.




DESIGN & FORMATING TOOLS : Our word-processing tools and design resources are made to simplify your content drafting and design journey while ensuring a professional and impressive public presentation.




QR-CODES & LINKS : We offer you scannable QR-codes and Links uniquely associated with every new domain you create to share and redirect your audience to your content domain with a simple scan or click.





Why INFO-CODE?
 

In today’s fast-paced world, traditional advertising methods like flyers, posters, brochuers, and banners often fall short of conveying comprehensive information, leaving potential customers with unanswered questions. Many advertisers rely on websites or phone calls to provide additional details, but these solutions frequently fail where in many cases websites may lack the promised content or not exist at all, and handling numerous inquiries over the phone is impractical and unreliable. Our platform bridges this gap by offering a centralized, dynamic solution for information hosting. With Info-code, advertisers, writters and content creators can create content domains with associated QR codes that direct their audiences to fully detailed and easily accessible screens and pages containing all the necessary information, ensuring that every inquiry is met with clarity and professionalism—without the hassle of maintaining a website or managing endless calls.






INFOCODES APPLICATION CASES

 


Unlock the Power of infocodes to Expand Accessibility Like Never Before.

Our domain-associated QR codes (infocodes) are your gateway to extended and instant access to valuable information. Whether you’re showcasing your business, sharing personal details, or enhancing user experiences, our Information domains redefine connectivity in various real-world applications as below.  

0. On your keyholders, profile tags, personalized keepsake or utility items. 



Host your business & products information, memories and sentimental content with us and print your scannable infocode linking to your content on personalized keepsakes or utility items.

1. On your Posters and Flyers 



Embedding your infocodes on marketing materials, like event posters or promotional flyers drives engagement beyond the paper. With one quick scan, users can access event schedules, product details, or special offers on your infocode domain keeping them engaged even after the poster is out of sight.  

2. On your Business Cards 



Transform your business card into a digital gateway by embedding our infocodes linked to your vCard and portfolio to share more than just contact details. Let clients instantly save your contact details, browse your work, or read more about your brand and influence.  

3. On your Live Broadcast 



Revolutionalize content sharing by embedding your domain-linked infocodes on a live broadcast/show to bridge the gap between traditional TV viewing and online content, creating a richer and more interactive audience experience allowing viewers to quickly access detailed news stories, multimedia content, or live updates.

4. On your Signposts and Billboards 



Enhance signposts or billboards with infocodes that lead to your additional information domain, or interactive content to maximize information in minimal space. For businesses like your's, this means potential customers can learn about your services, offers, and location without extra space on the sign.  

5. On your Identity and Access Cards 



Incorporating infocodes into your ID cards provides instant validation and access to extended profiles or credentials, perfect for events, institutions, or workplaces.  

6. On your Stamps and Seals  



Infocodes embedded in stamps on official documents or packages ensures authenticity while providing access to additional documentation or instructions.  

7. On your Product Packaging



Add infocodes to product labels or packaging to guide customers to user manuals, recipes, or detailed product specs. Build trust and engagement with transparency and creativity.  

8. On your Transactional Aggreements, Receipts and Invoices  



Elevate receipts with infocodes that link to warranty information, return policies, or even feedback forms—saving paper and improving customer satisfaction.  

9. On your Educational Materials  



Include infocodes on textbooks, presentation screens, or training manuals to offer access to supplementary materials, videos, or quizzes to extend learning horizons and enhance the learning experience.  

10. On your Personal Documents and Portfolios 



Whether it's a resume, an art portfolio, or a bio, infocodes can offer viewers an extended view of your work or profile, making you stand out.  

11. On your Community Boards and Public Notices 



Public announcements or community updates become more effective when infocodes link to detailed notices, event registrations, or contact forms, fostering better interaction.  

12. On your living room Wall frames 



Add infocodes to your wall frames to spice-up your living room serenity with a modern face of technology linking to your family memories from family celebrations to family tours and more.

13. On your Memorial Stones 



Add infocodes to your labels and memorial stones to preserve Legacies, literature and historical value for things and people to tell their story for generations. perfect for buiding commissioning, historical sites and tombtones. 




Create your content Domain profile now and join thousands of individuals and businesses using INFOCODE to meet your information sharing needs.


Get started today! Create, store, share, and validate your information with ease. Join the INFOCODE community today!



MAIN TITLE



Create Updates Payments
0
2
? Failed to send to cq12lBx-Rfq6qI94MFvsnD:APA91bHaHSRNax38gPuGuOoC91OT_stp32fLJfDYjl0-9p9BfLWQEBiR6DFya4TuYyA3JzJ6-fmr8nS1liaNB-FQwZ6TL0eBsm1H3zqFJUUjI5BURPzgh4o: The message could not be delivered to the device identified by 'cq12lBx-Rfq6qI94MFvsnD:APA91bHaHSRNax38gPuGuOoC91OT_stp32fLJfDYjl0-9p9BfLWQEBiR6DFya4TuYyA3JzJ6-fmr8nS1liaNB-FQwZ6TL0eBsm1H3zqFJUUjI5BURPzgh4o'. Although the token is syntactically correct, it is not known to the Firebase project you are using. This could have the following reasons: - The token has been unregistered from the project. This can happen when a user has logged out from the application on the given client, or if they have uninstalled or re-installed the application. - The token has been registered to a different Firebase project than the project you are using to send the message. A common reason for this is when you work with different application environments and are sending a message from one environment to a device in another environment.
? Failed to send to cq12lBx-Rfq6qI94MFvsnD:APA91bHaHSRNax38gPuGuOoC91OT_stp32fLJfDYjl0-9p9BfLWQEBiR6DFya4TuYyA3JzJ6-fmr8nS1liaNB-FQwZ6TL0eBsm1H3zqFJUUjI5BURPzgh4o: The message could not be delivered to the device identified by 'cq12lBx-Rfq6qI94MFvsnD:APA91bHaHSRNax38gPuGuOoC91OT_stp32fLJfDYjl0-9p9BfLWQEBiR6DFya4TuYyA3JzJ6-fmr8nS1liaNB-FQwZ6TL0eBsm1H3zqFJUUjI5BURPzgh4o'. Although the token is syntactically correct, it is not known to the Firebase project you are using. This could have the following reasons: - The token has been unregistered from the project. This can happen when a user has logged out from the application on the given client, or if they have uninstalled or re-installed the application. - The token has been registered to a different Firebase project than the project you are using to send the message. A common reason for this is when you work with different application environments and are sending a message from one environment to a device in another environment.
? Failed to send to cq12lBx-Rfq6qI94MFvsnD:APA91bHaHSRNax38gPuGuOoC91OT_stp32fLJfDYjl0-9p9BfLWQEBiR6DFya4TuYyA3JzJ6-fmr8nS1liaNB-FQwZ6TL0eBsm1H3zqFJUUjI5BURPzgh4o: The message could not be delivered to the device identified by 'cq12lBx-Rfq6qI94MFvsnD:APA91bHaHSRNax38gPuGuOoC91OT_stp32fLJfDYjl0-9p9BfLWQEBiR6DFya4TuYyA3JzJ6-fmr8nS1liaNB-FQwZ6TL0eBsm1H3zqFJUUjI5BURPzgh4o'. Although the token is syntactically correct, it is not known to the Firebase project you are using. This could have the following reasons: - The token has been unregistered from the project. This can happen when a user has logged out from the application on the given client, or if they have uninstalled or re-installed the application. - The token has been registered to a different Firebase project than the project you are using to send the message. A common reason for this is when you work with different application environments and are sending a message from one environment to a device in another environment.
? Failed to send to cq12lBx-Rfq6qI94MFvsnD:APA91bHaHSRNax38gPuGuOoC91OT_stp32fLJfDYjl0-9p9BfLWQEBiR6DFya4TuYyA3JzJ6-fmr8nS1liaNB-FQwZ6TL0eBsm1H3zqFJUUjI5BURPzgh4o: The message could not be delivered to the device identified by 'cq12lBx-Rfq6qI94MFvsnD:APA91bHaHSRNax38gPuGuOoC91OT_stp32fLJfDYjl0-9p9BfLWQEBiR6DFya4TuYyA3JzJ6-fmr8nS1liaNB-FQwZ6TL0eBsm1H3zqFJUUjI5BURPzgh4o'. Although the token is syntactically correct, it is not known to the Firebase project you are using. This could have the following reasons: - The token has been unregistered from the project. This can happen when a user has logged out from the application on the given client, or if they have uninstalled or re-installed the application. - The token has been registered to a different Firebase project than the project you are using to send the message. A common reason for this is when you work with different application environments and are sending a message from one environment to a device in another environment.
? Failed to send to cq12lBx-Rfq6qI94MFvsnD:APA91bHaHSRNax38gPuGuOoC91OT_stp32fLJfDYjl0-9p9BfLWQEBiR6DFya4TuYyA3JzJ6-fmr8nS1liaNB-FQwZ6TL0eBsm1H3zqFJUUjI5BURPzgh4o: The message could not be delivered to the device identified by 'cq12lBx-Rfq6qI94MFvsnD:APA91bHaHSRNax38gPuGuOoC91OT_stp32fLJfDYjl0-9p9BfLWQEBiR6DFya4TuYyA3JzJ6-fmr8nS1liaNB-FQwZ6TL0eBsm1H3zqFJUUjI5BURPzgh4o'. Although the token is syntactically correct, it is not known to the Firebase project you are using. This could have the following reasons: - The token has been unregistered from the project. This can happen when a user has logged out from the application on the given client, or if they have uninstalled or re-installed the application. - The token has been registered to a different Firebase project than the project you are using to send the message. A common reason for this is when you work with different application environments and are sending a message from one environment to a device in another environment.
? Failed to send to cq12lBx-Rfq6qI94MFvsnD:APA91bHaHSRNax38gPuGuOoC91OT_stp32fLJfDYjl0-9p9BfLWQEBiR6DFya4TuYyA3JzJ6-fmr8nS1liaNB-FQwZ6TL0eBsm1H3zqFJUUjI5BURPzgh4o: The message could not be delivered to the device identified by 'cq12lBx-Rfq6qI94MFvsnD:APA91bHaHSRNax38gPuGuOoC91OT_stp32fLJfDYjl0-9p9BfLWQEBiR6DFya4TuYyA3JzJ6-fmr8nS1liaNB-FQwZ6TL0eBsm1H3zqFJUUjI5BURPzgh4o'. Although the token is syntactically correct, it is not known to the Firebase project you are using. This could have the following reasons: - The token has been unregistered from the project. This can happen when a user has logged out from the application on the given client, or if they have uninstalled or re-installed the application. - The token has been registered to a different Firebase project than the project you are using to send the message. A common reason for this is when you work with different application environments and are sending a message from one environment to a device in another environment.
? Failed to send to cq12lBx-Rfq6qI94MFvsnD:APA91bHaHSRNax38gPuGuOoC91OT_stp32fLJfDYjl0-9p9BfLWQEBiR6DFya4TuYyA3JzJ6-fmr8nS1liaNB-FQwZ6TL0eBsm1H3zqFJUUjI5BURPzgh4o: The message could not be delivered to the device identified by 'cq12lBx-Rfq6qI94MFvsnD:APA91bHaHSRNax38gPuGuOoC91OT_stp32fLJfDYjl0-9p9BfLWQEBiR6DFya4TuYyA3JzJ6-fmr8nS1liaNB-FQwZ6TL0eBsm1H3zqFJUUjI5BURPzgh4o'. Although the token is syntactically correct, it is not known to the Firebase project you are using. This could have the following reasons: - The token has been unregistered from the project. This can happen when a user has logged out from the application on the given client, or if they have uninstalled or re-installed the application. - The token has been registered to a different Firebase project than the project you are using to send the message. A common reason for this is when you work with different application environments and are sending a message from one environment to a device in another environment.
? Failed to send to fu-vojdzQhyjfPNLbbJVMN:APA91bECvtv5alPg3DsVJjQh0E2B2YUDOPNGDcMtqKUBssLPeVbMPhB24ny3289SMLUTs3GT7i9d3TwR_w_Eq2RPbW8Wi38pIgsMWKcnYA0MOSvyToy7J3k: The message could not be delivered to the device identified by 'fu-vojdzQhyjfPNLbbJVMN:APA91bECvtv5alPg3DsVJjQh0E2B2YUDOPNGDcMtqKUBssLPeVbMPhB24ny3289SMLUTs3GT7i9d3TwR_w_Eq2RPbW8Wi38pIgsMWKcnYA0MOSvyToy7J3k'. Although the token is syntactically correct, it is not known to the Firebase project you are using. This could have the following reasons: - The token has been unregistered from the project. This can happen when a user has logged out from the application on the given client, or if they have uninstalled or re-installed the application. - The token has been registered to a different Firebase project than the project you are using to send the message. A common reason for this is when you work with different application environments and are sending a message from one environment to a device in another environment.
? Failed to send to fu-vojdzQhyjfPNLbbJVMN:APA91bECvtv5alPg3DsVJjQh0E2B2YUDOPNGDcMtqKUBssLPeVbMPhB24ny3289SMLUTs3GT7i9d3TwR_w_Eq2RPbW8Wi38pIgsMWKcnYA0MOSvyToy7J3k: The message could not be delivered to the device identified by 'fu-vojdzQhyjfPNLbbJVMN:APA91bECvtv5alPg3DsVJjQh0E2B2YUDOPNGDcMtqKUBssLPeVbMPhB24ny3289SMLUTs3GT7i9d3TwR_w_Eq2RPbW8Wi38pIgsMWKcnYA0MOSvyToy7J3k'. Although the token is syntactically correct, it is not known to the Firebase project you are using. This could have the following reasons: - The token has been unregistered from the project. This can happen when a user has logged out from the application on the given client, or if they have uninstalled or re-installed the application. - The token has been registered to a different Firebase project than the project you are using to send the message. A common reason for this is when you work with different application environments and are sending a message from one environment to a device in another environment.
? Failed to send to eCeUtmJsQ-WsPYX9Ysn9xn:APA91bGXmRzyjhnsrlZF8ItLP6yHj_sTSqNOcx2bNKu12ekKF9t_U2YmO211HTRMKLVa5eZ1R8ivku8fpKnunWQxOipOTVaSkqr0hvPKbzAvAKZ_69d4mHY: The message could not be delivered to the device identified by 'eCeUtmJsQ-WsPYX9Ysn9xn:APA91bGXmRzyjhnsrlZF8ItLP6yHj_sTSqNOcx2bNKu12ekKF9t_U2YmO211HTRMKLVa5eZ1R8ivku8fpKnunWQxOipOTVaSkqr0hvPKbzAvAKZ_69d4mHY'. Although the token is syntactically correct, it is not known to the Firebase project you are using. This could have the following reasons: - The token has been unregistered from the project. This can happen when a user has logged out from the application on the given client, or if they have uninstalled or re-installed the application. - The token has been registered to a different Firebase project than the project you are using to send the message. A common reason for this is when you work with different application environments and are sending a message from one environment to a device in another environment.
? Failed to send to eCeUtmJsQ-WsPYX9Ysn9xn:APA91bGXmRzyjhnsrlZF8ItLP6yHj_sTSqNOcx2bNKu12ekKF9t_U2YmO211HTRMKLVa5eZ1R8ivku8fpKnunWQxOipOTVaSkqr0hvPKbzAvAKZ_69d4mHY: The message could not be delivered to the device identified by 'eCeUtmJsQ-WsPYX9Ysn9xn:APA91bGXmRzyjhnsrlZF8ItLP6yHj_sTSqNOcx2bNKu12ekKF9t_U2YmO211HTRMKLVa5eZ1R8ivku8fpKnunWQxOipOTVaSkqr0hvPKbzAvAKZ_69d4mHY'. Although the token is syntactically correct, it is not known to the Firebase project you are using. This could have the following reasons: - The token has been unregistered from the project. This can happen when a user has logged out from the application on the given client, or if they have uninstalled or re-installed the application. - The token has been registered to a different Firebase project than the project you are using to send the message. A common reason for this is when you work with different application environments and are sending a message from one environment to a device in another environment.
? Failed to send to eCeUtmJsQ-WsPYX9Ysn9xn:APA91bGXmRzyjhnsrlZF8ItLP6yHj_sTSqNOcx2bNKu12ekKF9t_U2YmO211HTRMKLVa5eZ1R8ivku8fpKnunWQxOipOTVaSkqr0hvPKbzAvAKZ_69d4mHY: The message could not be delivered to the device identified by 'eCeUtmJsQ-WsPYX9Ysn9xn:APA91bGXmRzyjhnsrlZF8ItLP6yHj_sTSqNOcx2bNKu12ekKF9t_U2YmO211HTRMKLVa5eZ1R8ivku8fpKnunWQxOipOTVaSkqr0hvPKbzAvAKZ_69d4mHY'. Although the token is syntactically correct, it is not known to the Firebase project you are using. This could have the following reasons: - The token has been unregistered from the project. This can happen when a user has logged out from the application on the given client, or if they have uninstalled or re-installed the application. - The token has been registered to a different Firebase project than the project you are using to send the message. A common reason for this is when you work with different application environments and are sending a message from one environment to a device in another environment.
? Failed to send to eCeUtmJsQ-WsPYX9Ysn9xn:APA91bGXmRzyjhnsrlZF8ItLP6yHj_sTSqNOcx2bNKu12ekKF9t_U2YmO211HTRMKLVa5eZ1R8ivku8fpKnunWQxOipOTVaSkqr0hvPKbzAvAKZ_69d4mHY: The message could not be delivered to the device identified by 'eCeUtmJsQ-WsPYX9Ysn9xn:APA91bGXmRzyjhnsrlZF8ItLP6yHj_sTSqNOcx2bNKu12ekKF9t_U2YmO211HTRMKLVa5eZ1R8ivku8fpKnunWQxOipOTVaSkqr0hvPKbzAvAKZ_69d4mHY'. Although the token is syntactically correct, it is not known to the Firebase project you are using. This could have the following reasons: - The token has been unregistered from the project. This can happen when a user has logged out from the application on the given client, or if they have uninstalled or re-installed the application. - The token has been registered to a different Firebase project than the project you are using to send the message. A common reason for this is when you work with different application environments and are sending a message from one environment to a device in another environment.
? Failed to send to eCeUtmJsQ-WsPYX9Ysn9xn:APA91bGXmRzyjhnsrlZF8ItLP6yHj_sTSqNOcx2bNKu12ekKF9t_U2YmO211HTRMKLVa5eZ1R8ivku8fpKnunWQxOipOTVaSkqr0hvPKbzAvAKZ_69d4mHY: The message could not be delivered to the device identified by 'eCeUtmJsQ-WsPYX9Ysn9xn:APA91bGXmRzyjhnsrlZF8ItLP6yHj_sTSqNOcx2bNKu12ekKF9t_U2YmO211HTRMKLVa5eZ1R8ivku8fpKnunWQxOipOTVaSkqr0hvPKbzAvAKZ_69d4mHY'. Although the token is syntactically correct, it is not known to the Firebase project you are using. This could have the following reasons: - The token has been unregistered from the project. This can happen when a user has logged out from the application on the given client, or if they have uninstalled or re-installed the application. - The token has been registered to a different Firebase project than the project you are using to send the message. A common reason for this is when you work with different application environments and are sending a message from one environment to a device in another environment.
? Failed to send to eCeUtmJsQ-WsPYX9Ysn9xn:APA91bGXmRzyjhnsrlZF8ItLP6yHj_sTSqNOcx2bNKu12ekKF9t_U2YmO211HTRMKLVa5eZ1R8ivku8fpKnunWQxOipOTVaSkqr0hvPKbzAvAKZ_69d4mHY: The message could not be delivered to the device identified by 'eCeUtmJsQ-WsPYX9Ysn9xn:APA91bGXmRzyjhnsrlZF8ItLP6yHj_sTSqNOcx2bNKu12ekKF9t_U2YmO211HTRMKLVa5eZ1R8ivku8fpKnunWQxOipOTVaSkqr0hvPKbzAvAKZ_69d4mHY'. Although the token is syntactically correct, it is not known to the Firebase project you are using. This could have the following reasons: - The token has been unregistered from the project. This can happen when a user has logged out from the application on the given client, or if they have uninstalled or re-installed the application. - The token has been registered to a different Firebase project than the project you are using to send the message. A common reason for this is when you work with different application environments and are sending a message from one environment to a device in another environment.
? Failed to send to eCeUtmJsQ-WsPYX9Ysn9xn:APA91bGXmRzyjhnsrlZF8ItLP6yHj_sTSqNOcx2bNKu12ekKF9t_U2YmO211HTRMKLVa5eZ1R8ivku8fpKnunWQxOipOTVaSkqr0hvPKbzAvAKZ_69d4mHY: The message could not be delivered to the device identified by 'eCeUtmJsQ-WsPYX9Ysn9xn:APA91bGXmRzyjhnsrlZF8ItLP6yHj_sTSqNOcx2bNKu12ekKF9t_U2YmO211HTRMKLVa5eZ1R8ivku8fpKnunWQxOipOTVaSkqr0hvPKbzAvAKZ_69d4mHY'. Although the token is syntactically correct, it is not known to the Firebase project you are using. This could have the following reasons: - The token has been unregistered from the project. This can happen when a user has logged out from the application on the given client, or if they have uninstalled or re-installed the application. - The token has been registered to a different Firebase project than the project you are using to send the message. A common reason for this is when you work with different application environments and are sending a message from one environment to a device in another environment.
? Failed to send to eCeUtmJsQ-WsPYX9Ysn9xn:APA91bGXmRzyjhnsrlZF8ItLP6yHj_sTSqNOcx2bNKu12ekKF9t_U2YmO211HTRMKLVa5eZ1R8ivku8fpKnunWQxOipOTVaSkqr0hvPKbzAvAKZ_69d4mHY: The message could not be delivered to the device identified by 'eCeUtmJsQ-WsPYX9Ysn9xn:APA91bGXmRzyjhnsrlZF8ItLP6yHj_sTSqNOcx2bNKu12ekKF9t_U2YmO211HTRMKLVa5eZ1R8ivku8fpKnunWQxOipOTVaSkqr0hvPKbzAvAKZ_69d4mHY'. Although the token is syntactically correct, it is not known to the Firebase project you are using. This could have the following reasons: - The token has been unregistered from the project. This can happen when a user has logged out from the application on the given client, or if they have uninstalled or re-installed the application. - The token has been registered to a different Firebase project than the project you are using to send the message. A common reason for this is when you work with different application environments and are sending a message from one environment to a device in another environment.
? Failed to send to fB_zYEMmRyGlAgyrKZ3DOH:APA91bGylBO3UxVtNooadGLIGEp6czaSYEAPfYGsEHo9jbsJlq1jSj5ko4nzuCtXjjkky3KRBDDONZA3_p3w4EEIKbTw4eA8qFVrNV5VcXEiup4-UvKW6ws: The message could not be delivered to the device identified by 'fB_zYEMmRyGlAgyrKZ3DOH:APA91bGylBO3UxVtNooadGLIGEp6czaSYEAPfYGsEHo9jbsJlq1jSj5ko4nzuCtXjjkky3KRBDDONZA3_p3w4EEIKbTw4eA8qFVrNV5VcXEiup4-UvKW6ws'. Although the token is syntactically correct, it is not known to the Firebase project you are using. This could have the following reasons: - The token has been unregistered from the project. This can happen when a user has logged out from the application on the given client, or if they have uninstalled or re-installed the application. - The token has been registered to a different Firebase project than the project you are using to send the message. A common reason for this is when you work with different application environments and are sending a message from one environment to a device in another environment.
? Failed to send to fB_zYEMmRyGlAgyrKZ3DOH:APA91bGylBO3UxVtNooadGLIGEp6czaSYEAPfYGsEHo9jbsJlq1jSj5ko4nzuCtXjjkky3KRBDDONZA3_p3w4EEIKbTw4eA8qFVrNV5VcXEiup4-UvKW6ws: The message could not be delivered to the device identified by 'fB_zYEMmRyGlAgyrKZ3DOH:APA91bGylBO3UxVtNooadGLIGEp6czaSYEAPfYGsEHo9jbsJlq1jSj5ko4nzuCtXjjkky3KRBDDONZA3_p3w4EEIKbTw4eA8qFVrNV5VcXEiup4-UvKW6ws'. Although the token is syntactically correct, it is not known to the Firebase project you are using. This could have the following reasons: - The token has been unregistered from the project. This can happen when a user has logged out from the application on the given client, or if they have uninstalled or re-installed the application. - The token has been registered to a different Firebase project than the project you are using to send the message. A common reason for this is when you work with different application environments and are sending a message from one environment to a device in another environment.
? Failed to send to fB_zYEMmRyGlAgyrKZ3DOH:APA91bGylBO3UxVtNooadGLIGEp6czaSYEAPfYGsEHo9jbsJlq1jSj5ko4nzuCtXjjkky3KRBDDONZA3_p3w4EEIKbTw4eA8qFVrNV5VcXEiup4-UvKW6ws: The message could not be delivered to the device identified by 'fB_zYEMmRyGlAgyrKZ3DOH:APA91bGylBO3UxVtNooadGLIGEp6czaSYEAPfYGsEHo9jbsJlq1jSj5ko4nzuCtXjjkky3KRBDDONZA3_p3w4EEIKbTw4eA8qFVrNV5VcXEiup4-UvKW6ws'. Although the token is syntactically correct, it is not known to the Firebase project you are using. This could have the following reasons: - The token has been unregistered from the project. This can happen when a user has logged out from the application on the given client, or if they have uninstalled or re-installed the application. - The token has been registered to a different Firebase project than the project you are using to send the message. A common reason for this is when you work with different application environments and are sending a message from one environment to a device in another environment.