-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MqttOverWS - Error handling message in node_modules/.vite/deps/@aws-amplify_pubsub.js #13463
Comments
same on my end using the version below
|
Hey, @paulinesarana19 👋. Can you share a code snippet where you're using the mqttTopicMatch? Working on reproducing this on a Gen 1 app using v6 of Amplify. CC: @rjuevesano |
I'm using svelte and here's my code snippet. $lib/pubsub.ts
+layout.svelte
Calling PubSub directly without creating a separate export function won't return a warning/error and it's working properly. +layout.svelte
|
I've been trying to reproduce this to no avail but have been trying to dig into the dependencies and compatibility on v6 based on OP's environment information. @rjuevesano, can you share your |
Closing this issue as we have not heard back from you. If you are still experiencing this, please feel free to reply back and provide any information previously requested and we'd be happy to re-open the issue. Thank you! |
Before opening, please confirm:
JavaScript Framework
Not applicable
Amplify APIs
PubSub
Amplify Version
v6
Amplify Categories
notifications
Backend
Other
Environment information
Describe the bug
When receiving messages on a subscribed PubSub topic, an error warning is thrown
filter2.split is not a function at mqttTopicMatch...
.This hasn't happened before with the same setup. boto3 is used to publish a message. Svelte is used as web framework.
Expected behavior
There should be no issue even when a basic dictionary is published as a message.
Reproduction steps
Code Snippet
// Put your code below this line.
Log output
aws-exports.js
import { env } from '$env/dynamic/public';
export default {
aws_project_region: AWS_PROJECT_REGION,
aws_cognito_identity_pool_id: AWS_COGNITO_IDENTITY_POOL_ID,
aws_cognito_region: AWS_COGNITO_REGION,
aws_user_pools_id: AWS_USER_POOLS_ID,
aws_user_pools_web_client_id: AWS_USER_POOLS_WEB_CLIENT_ID,
oauth: {},
aws_cognito_username_attributes: ['EMAIL'],
aws_cognito_social_providers: [],
aws_cognito_signup_attributes: ['EMAIL'],
aws_cognito_mfa_configuration: 'OFF',
aws_cognito_mfa_types: ['SMS'],
aws_cognito_password_protection_settings: {
passwordPolicyMinLength: 8,
passwordPolicyCharacters: []
},
aws_cognito_verification_mechanisms: ['EMAIL']
};
Manual configuration
No response
Additional configuration
No response
Mobile Device
No response
Mobile Operating System
No response
Mobile Browser
No response
Mobile Browser Version
No response
Additional information and screenshots
No response
The text was updated successfully, but these errors were encountered: