Skip to content

/ Amplitude-JavaScript

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

Jump to bottom

Modified apiEndpoint breaks Amplitude Instrumentation Explorer #310

Open
Naismith opened this issue Oct 20, 2020 · 5 comments
Open

Modified apiEndpoint breaks Amplitude Instrumentation Explorer #310

Naismith opened this issue Oct 20, 2020 · 5 comments
Assignees
@jooohhn
Labels
bug

Comments

@Naismith
Copy link

@Naismith Naismith commented Oct 20, 2020

Expected Behavior

Expect events to be tracked using the new apiEndpoint provided

Current Behavior

No events are shown in the plugin

Possible Solution

Allow JS SDK or Plugin to change apiEndpoint for watching the talks

Steps to Reproduce

  1. init client with a custom apiEndpoint in config
  2. open plugin in chrome to no events

Environment

  • JS SDK Version: 7.1.0
  • Installation Method: Yarn
  • Browser and Version or React Native and Device: Chrome 84 - MacOS Catalina 10.15.6
@Naismith Naismith added the bug label Oct 20, 2020
@jooohhn
Copy link
Member

@jooohhn jooohhn commented Oct 22, 2020

Thanks for the report, will look into this
@jooohhn jooohhn self-assigned this Oct 22, 2020
@kelvin-lu
Copy link
Contributor

@kelvin-lu kelvin-lu commented Oct 22, 2020 •
edited

@Naismith are you using a custom endpoint or api2.amplitude.com? Version 0.1.2 of the instrumentation explorer should be able to listen to events on api2.amplitude.com, but we can keep this open to consider more generic api endpoints.
@Naismith
Copy link
Author

@Naismith Naismith commented Oct 22, 2020

@Naismith are you using a custom endpoint or api2.amplitude.com? Version 0.1.2 of the instrumentation explorer should be able to listen to events on api2.amplitude.com, but we can keep this open to consider more generic api endpoints.

I am using a custom endpoint
@Naismith
Copy link
Author

@Naismith Naismith commented Nov 2, 2020

@jooohhn and @kelvin-lu has there been any progress on this? Just checking in.
@kelvin-lu
Copy link
Contributor

@kelvin-lu kelvin-lu commented Nov 3, 2020 •
edited

Hey @Naismith, apologies for the lack of communication here but we're tracking this issue internally as well - we're hoping to have updates this week or in the coming week so that the instrumentation explorer can be configured to other endpoints!
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jooohhn jooohhn

Labels
bug
Projects
None yet
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
@Naismith @jooohhn @kelvin-lu
You can’t perform that action at this time.