♠️
RACE Protocol
NFT PresaleDiscord
  • ❤️Official Docs & Links
  • ⏳Progress Overview
  • RACE Protocol
    • 🏗️System Architecture
      • Components
      • On-chain Accounts
      • Synchronization
      • Randomization
      • Payment
    • 🎲Game Development
      • Game Handler
      • Effect
      • Event Handling
      • Race API
        • Arweave Integration
      • Race JS SDK
        • Installation and Setup
        • Key Components
          • AppClient
          • SubClient
          • Events
          • Game Context
          • Decryption Cache
        • Advanced Features
          • Getting Revealed Knowledge
          • Exiting and Detaching
          • Submitting Messages
          • Sub-game Interaction
        • Best Practices
        • API Reference
        • Troubleshooting
    • 🧪Testing
      • Race Test Kit
      • Unit Testing
      • Integration Testing
      • Additional Considerations
    • 🧱Modules & Features
      • Encryption Methods
      • Command-line Tools
      • Configuration Options
      • Blockchain Transport Implementations
    • 📃Smart Contract
      • Solana Program
    • 🔦Examples and Use Cases
      • Draw Card Game
      • Raffle Game
      • Other Examples
  • RACE Games
    • ♠️RACE Poker app
      • 🎮Start playing in minutes
        • 💰Cash and sit-n-go
        • 🏆Tournaments
      • 🎨Workshop
        • 🏆Create cash games
        • 🏨Create tourneys
      • 💡Concept introduction
      • 🏗️System architecture
      • 👾Game Flow
      • 🎲Cards shuffling
      • ☎️Communication
      • 🔐Key sharing/decryption
      • 💱Cash flow structure
    • ⚡Solfast
      • 🎲Game modes
  • RACE RESEARCH
    • 👾No-Code Development
      • Brainstorming
      • Implementation Approach
      • Project Status
    • 0️⃣Zero-Knowledge Proofs
      • Brainstorming
      • Integration steps
        • Verifiable Randomness Generation
        • Private Game State Updates
        • Verifiable Settlements
        • Private Player Actions
      • Project Status
    • 🛡️Security Audit Report
      • Executive summary
        • Introduction to Race Protocol
        • Audit Methodology
      • Findings
        • Smart Contract Security
        • WebAssembly Security
        • Client-side Security (Race SDK)
        • Server-side Security
        • Randomization and Encryption
        • On-chain Account Management
        • Synchronization Mechanisms
        • Payment Handling
      • Recommendations
      • Conclusion
  • RACE DAO
    • 😎About
    • 🫂Community
    • 🖼️NFT Collection [!]
Powered by GitBook
On this page
  • Troubleshooting Common Issues
  • Community Resources and Support
  1. RACE Protocol
  2. Game Development
  3. Race JS SDK

Troubleshooting

Troubleshooting Common Issues

Here are some common issues you may encounter when using the RACE JS SDK and guidance on troubleshooting them:

  • Connection Errors:

    • Check the Transactor endpoint: Ensure that the endpoint URL provided during initialization is correct and accessible.

    • Verify network connectivity: Make sure your client application has a stable internet connection.

    • Inspect error logs: Check the browser console or server logs for any error messages related to the websocket connection.

  • Game Bundle Loading Errors:

    • Verify the game bundle address: Ensure that the game bundle address is correct and the bundle is published on the blockchain.

    • Check decentralized storage accessibility: Make sure the decentralized storage solution (e.g., IPFS, Arweave) is accessible and the game bundle data can be retrieved.

    • Inspect WASM loading errors: Check the browser console or server logs for any errors related to loading or executing the WASM game bundle.

  • Event Handling Issues:

    • Verify event listener registration: Ensure that you have correctly registered event listeners using the onEvent function of the AppClient or SubClient.

    • Check event data format: Make sure that the custom events you are submitting are serialized correctly and match the format expected by the game handler.

    • Debug game state updates: Use console logs or debugging tools to inspect the game state updates in response to events and verify that they are happening as expected.

  • Decryption Errors:

    • Verify secret keys: Ensure that the player has the correct secret keys for decrypting the revealed hidden knowledge.

    • Check decryption logic: Review the decryption logic in your client application and ensure that it is implemented correctly.

Community Resources and Support

If you encounter issues that you cannot resolve through troubleshooting, you can seek further assistance from the Race Protocol community and support channels:

  • Race Protocol Documentation: Refer to the official Race Protocol documentation for detailed information about the protocol, SDK usage, and troubleshooting tips.

By utilizing these resources and support channels, you can get help with troubleshooting issues and learn from the experiences of other developers using the RACE JS SDK.

PreviousAPI ReferenceNextTesting

Last updated 1 year ago

Race Discord Server: Join the to connect with the developer community, ask questions, and get help from other developers and the core team.

GitHub Repository: Visit the to report bugs, suggest improvements, and contribute to the project's development.

🎲
Race Discord server
Race Protocol GitHub repository