Sync stream is not working despite setting the config: edition: 2

[KarthikRaju391]

I am getting the following error when I try to connect from the react native client:

{"bson":false,"client_id":"30ca26a2-d0e4-4078-a6e3-b747b6d8ff25","errorData":{"code":"PSYNC_S2302","description":"No sync rules available","name":"ServiceError","status":500},"is_service_error":true,"level":"error","message":"Request failed [PSYNC_S2302] No sync rules available","name":"ServiceError","rid":"h/019a2a4b-15b9-71b4-9329-c09d75d4ba09","route":"/sync/stream","stack":"ServiceError: [PSYNC_S2302] No sync rules available\n    at Object.handler (file:///app/packages/service-core/dist/routes/endpoints/sync-stream.js:50:19)\n    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\n    at async Object.handler (file:///app/packages/service-core/dist/routes/route-register.js:37:50)","timestamp":"2025-10-28T10:09:15.200Z","user_agent":"powersync-js/1.39.0 powersync-react-native react-native/0.79 android/36","user_id":"65b7a43b247ad503323181b5"}

I have updated the powersync react native sdk to version 1.25.0 and using the rust based sync implementation as mentioned in the docs.

[simolus3]

Do you see any errors in the service logs for the PowerSync service? These would typically have more details when there's a configuration error preventing the service from starting.

[KarthikRaju391]

I have powersync deployed on docker and the error is from the service logs on docker itself

[simolus3]

Oh right 😅 Are there any additional errors while the service starts up? Did this only start happening after you've adopted sync streams? Can you share the configuration YAML file you have for the service (you can remove the connections settings / any credentials).

[KarthikRaju391]

Initially I get an info message saying that there are no sync rules and that's it.

Here are the two setups I tried:

replication:
  connections:
    - type: postgresql
      uri: !env PS_DATA_SOURCE_URI
      # Add these connection pool settings
      connection_timeout: 30
      keepalives: 1
      keepalives_idle: 10
      keepalives_interval: 10
      keepalives_count: 5
      # SSL settings
      sslmode: disable # 'verify-full' (default) or 'verify-ca' or 'disable'

# Connection settings for sync bucket storage
storage:
  type: mongodb
  uri: mongodb://mongo:27017/powersync_demo

# The port which the PowerSync API server will listen on
port: !env PS_PORT

# Specify sync streams
config:
  edition: 2

streams:
  # Synced conversations
  user_conversations:
    query: SELECT * FROM conversations WHERE id IN (SELECT conversation_id FROM conversation_participants WHERE user_id = auth.user_id() AND status = 'active')
    auto_subscribe: true

  # Conversation roles in user's conversations
  user_conversation_roles:
    query: SELECT * FROM conversation_roles WHERE conversation_id IN (SELECT conversation_id FROM conversation_participants WHERE user_id = auth.user_id() AND status = 'active')
    auto_subscribe: true

  # Role permissions for roles in user's conversations
  user_role_permissions:
    query: SELECT * FROM role_permissions WHERE conversation_role_id IN (SELECT id FROM conversation_roles WHERE conversation_id IN (SELECT conversation_id FROM conversation_participants WHERE user_id = auth.user_id() AND status = 'active'))
    auto_subscribe: true

# Settings for client authentication
client_auth:
  # Enable this if using Supabase Auth
  supabase: false

  # JWKS configuration matching your chat server
  jwks:
    keys:
      - kty: oct
        alg: "HS256"
        # Removed kid since Elixir server doesn't set it
        k: !env PS_JWT_SECRET_KEY

And tried to nest the streams inside sync rules option like this:

sync_rules:
  config:
    edition: 2
  streams: 
    # Synced conversations
    user_conversations:
      query: SELECT * FROM conversations WHERE id IN (SELECT conversation_id FROM conversation_participants WHERE user_id = auth.user_id() AND status = 'active')
      auto_subscribe: true

    # Conversation roles in user's conversations
    user_conversation_roles:
      query: SELECT * FROM conversation_roles WHERE conversation_id IN (SELECT conversation_id FROM conversation_participants WHERE user_id = auth.user_id() AND status = 'active')
      auto_subscribe: true

    # Role permissions for roles in user's conversations
    user_role_permissions:
      query: SELECT * FROM role_permissions WHERE conversation_role_id IN (SELECT id FROM conversation_roles WHERE conversation_id IN (SELECT conversation_id FROM conversation_participants WHERE user_id = auth.user_id() AND status = 'active'))
      auto_subscribe: true

[simolus3]

Streams as a top-level key wouldn't work. The second definition looks correct to me though. In most of our setups we define sync rules in a separate file and then use

sync_rules:
  # This path is relative to the `powersync.yaml` file
  path: sync-rules.yaml

I'm not sure if the single-file approach is supposed to work, but if it worked before migrating to sync streams it probably is :D Which version of the PowerSync service image are you using? Since sync streams are a new feature, it's possible you can't use them because Docker used an image you've pulled before.

[KarthikRaju391]

I am using the latest docker image of powersync and I tried deleting the old image and reinstalling.
I even tried manually setting the latest version number in the image definition.

[rkistner]

For the single-file approach, you need to provide the sync rules as text content, like this:

sync_rules:
  # The | pipe character here is important, indicating it's multi-line text
  content: |
    config:
      edition: 2
    streams:
      # ...

Due to the potential for easy-to-miss mistakes here, I recommend using the split file approach.