FG
πŸ”Œ

APIs & SDKs

259 verified issues

πŸ”Œ APIs & SDKsGoogle
Freshabout 18 hours ago

Firestore import - Bundle size is huge

import firebase from '@firebase/app'; import '@firebase/firestore'; // this one is very very huge. I am using only firestore in my app. How to reduce the bundle size of firestore?

Confidence95%
95%
Candidate Fix
1 fix
πŸ”Œ APIs & SDKs
Freshabout 18 hours ago

Don't send default header

If a header has been set as a default, there does not appear to be any way to skip it on an individual request. Setting `null` or `undefined` doesn't do anything.

Confidence95%
95%
Candidate Fix
1 fix
πŸ”Œ APIs & SDKsGoogle
Freshabout 18 hours ago

FR: Firestore OR operator in WHERE query

[REQUIRED] Describe your environment Operating System version: N/A Firebase SDK version: 4.6.2 * Firebase Product: firestore [REQUIRED] Describe the problem Rather than having to make several separate queries I would like to see an OR operator for the WHERE query in Firestore. This is something that is currently available in MongoDB or with the $or operator here. Relevant Code: The query could look something like this: [code block] or better yet [code block]

Confidence95%
95%
Candidate Fix
1 fix
πŸ”Œ APIs & SDKsGoogle
Freshabout 18 hours ago

Typescript definition file

Could you include the d.ts file in this client distribution?

Confidence95%
95%
Candidate Fix
1 fix
πŸ”Œ APIs & SDKs
Freshabout 18 hours ago

Compile error with webpack 4

Hi, After updating to webpack 4, compiling graphiql doesn't work because of the graphql-js dependency. I get a bunch of those errors: [code block] (and a million more) Seems like forcing the downgrade to a graphql-js version that doesn't have .mjs files fixes the issue.

Confidence95%
95%
Candidate Fix
1 fix
πŸ”Œ APIs & SDKs
Freshabout 18 hours ago

responseType: 'text' return Json Object

[code block] But: [code block] - axios version: v0.16.1

Confidence95%
95%
Candidate Fix
1 fix
πŸ”Œ APIs & SDKs
Freshabout 18 hours ago

Getting 'Cross-Origin Request Blocked' on a GET request

Summary I'm making a GET request to 4chan's API for retrieving threads from a board. This is my code: [code block] I receive the following warning: `Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://a.4cdn.org/a/threads.json. (Reason: CORS header β€˜Access-Control-Allow-Origin’ missing). ` As seen above, I have added the relevant header, but it does not solve the issue. I made the same request from my terminal using cURL and it worked fine. Context - axios version: e.g.: v0.16.0 - Environment: e.g.: node v6.9.4, Firefox 51.0.1, Ubuntu 14.04

Confidence95%
95%
Candidate Fix
1 fix
πŸ”Œ APIs & SDKs
Freshabout 18 hours ago

Setting header: 'Content-Type': 'application/json' is not working

Hi. I'm passing a custom header like this [code block] But it doesn't seem to work. Any ideas?

Confidence95%
95%
Candidate Fix
1 fix
πŸ”Œ APIs & SDKs
Freshabout 18 hours ago

Request to HTTPS with HTTP proxy fails

Summary Trying to do a HTTPS request with a HTTP proxy fails. [code block] Results in: [code block] The problem is already described by @chovy in this ticket, which ended up closed as OP did not have the same problem: https://github.com/mzabriskie/axios/issues/662 @chovy says: > I still have this issue not being able to hit an https url with an http proxy. I can do it fine in request and also in curl from shell. Something not working with axios. I get an EPROTO error. Context - axios version: v0.16.1 - Environment: node v7.10.0, Mac OSX Sierra

Confidence95%
95%
Candidate Fix
1 fix
πŸ”Œ APIs & SDKsGoogle
Freshabout 18 hours ago

Login to Firebase does not work on Safari 16.1+

Describe your environment Operating System version: Mac OS 12.6 Browser version: Safari 16.1 Firebase SDK version: 9.10.0 Firebase Product: auth Describe the problem Steps to reproduce: Try logging in to a site using `signInWithRedirect`. Notably it redirects back to the site without an error, and does not log the user in. Checking `getRedirectResult` returns a null user. This seems like a severe issue as iOS 16.1 will be released next week and presumably this issue will affect all those iOS users. Notably there seems to be a workaround of using `signInWithPopup`. It seems to work for us, though it is unclear why. Relevant Code: [code block]

Confidence95%
95%
Candidate Fix
1 fix
πŸ”Œ APIs & SDKs
Freshabout 18 hours ago

Property 'Authorization' does not exists on type 'AxiosHeaders' after upgrade to 1.2.2

Summary I'm getting the following error after upgrading axios to version 1.2.2: > TS2339: Property 'Authorization' does not exist on type 'AxiosHeaders | Partial<RawAxiosHeaders & MethodsHeaders & CommonHeaders>'. > Property 'Authorization' does not exist on type 'AxiosHeaders' The same snippet of code is working on version 1.2.1: [code block] Environment - Axios 1.2.2 - Node.js 18.12.1 - OS: Ubuntu 20.04.4 LTS (WSL2)

Confidence95%
95%
Candidate Fix
2 fixes
πŸ”Œ APIs & SDKs
Freshabout 18 hours ago

[Community Contest] A logo for Axios

Axios has grown to become a popular library with over 3 million weekly downloads on npm. I think it's time axios has its own logo, just like many other major libraries out there. I've designed a concept for the logo, and I hope you guys like it. The logo is based on the concept of request and response. The first one is a square icon/profile picture. The second and third are full logos. These images are not full size, so if you do like them and plan to use them, I can send you the full sized files. Edit: Should we count πŸ‘ reactions to this parent comment as votes for this logo submission, or just people in favor of a new logo in general? I can make a a second comment for votes for this submission, or we can do a proper poll with strawpoll later when people are done submitting their ideas.

Confidence95%
95%
Candidate Fix
1 fix
πŸ”Œ APIs & SDKs
Freshabout 18 hours ago

Feature request: fetch based adapter

I didn't see an issue for this (opened or closed), but if this is a duplicate just close it 😸 . Are there any plans for a `fetch` based adapter for axios? I thought I'd check and see if this has been discussed, and if not, if you all would be open to a feature request (or I'm happy to work on it and PR it). Reasons for adding a `fetch` adapter are basically for the same reasons you'd use fetch: - Support for service workers - Integration with Cache API - natively promise based, so axios can become a thinner library - response streaming - probably more that I'm not even thinking of right now Reasons you'd still want axios wrapping fetch for you (because some people feel like you don't need a lib over fetch): - fetch is low level. Using plain fetch in an app that is 99% GET/PUT/POST against a JSON API means lots of duplicate boilerplate code which axios can abstract - request/response interceptors - probably more that I'm not even thinking of right now :smile:

Confidence95%
95%
Candidate Fix
1 fix
πŸ”Œ APIs & SDKs
Freshabout 18 hours ago

Project dead?

Is the project dead? Are new maintainers sought? - 97 open pull requests - 411 open issues

Confidence95%
95%
Candidate Fix
1 fix
πŸ”Œ APIs & SDKsStripe
Freshabout 18 hours ago

Feature requests: Typescript definitions

Hi, Since typescript popularity is on the rise and there are no community definitions available for stripe-node I would very much like Typescript definitions. This will help both Typescript users and normal JS users with IDEs that support them like WebStorm and VSCode (even Sublime and Atom have JS hinting plugins that support them). I find using type definitions much easier than going through the documentation. In addition not all the documentation is up to date since I see the functions can optionally return promises if a callback is not passed and it's not documented.

Confidence95%
95%
Candidate Fix
1 fix
πŸ”Œ APIs & SDKsGoogle
Freshabout 18 hours ago

Firebase Auth is no longer working in incognito mode

[REQUIRED] Describe your environment Operating System version: Windows 10 Browser version: Version 81.0.4044.129 (Official Build) (64-bit) Firebase SDK version: 7.13.1 Firebase Product: auth [REQUIRED] Describe the problem Multiple of our users has reported, they are no longer able to login and use our product... After some investigation, it seems to happen for all the users, which accesses our platform in incognito mode. It seems to no longer be possible to use the firebase auth SDK in Google Incognito mode. The exact same users can log in with the exact same credentials or SSO integrations through firebase in non-incognito. Steps to reproduce: If users try to use firebase authentication on our platform in incognito mode, the error: `{code: "auth/web-storage-unsupported", message: "This browser is not supported or 3rd party cookies and data may be disabled.", a: null}` is thrown from the SDK. I believe it potentially can be an issue in a newer Chrome update, as I know Google has been experimenting with having Chrome block 3rd Party Cookies (I believe they experimented with it in version 83 of Chrome, which I am not using though).

Confidence95%
95%
Candidate Fix
1 fix
πŸ”Œ APIs & SDKs
Freshabout 18 hours ago

AxiosError: maxContentLength size of -1 exceeded

Doing an axiosRequest with const a = await axios.get(URL) and without any further configuration, it gives error: ' AxiosError: maxContentLength size of -1 exceeded' The contentLength of the website is significant, >185KB, but as I did not configure any maxContentLength then this behaviour is nonsense. What's the fix? Tried configuring a huge maxContentLength but still shows the error

Confidence95%
95%
Candidate Fix
2 fixes
πŸ”Œ APIs & SDKsGoogle
Freshabout 18 hours ago

Setting a timer for a long period of time, i.e. multiple minutes

I want to use firebase auth with react native for Login and Signup but I got a yellow error: Setting a timer for a long period of time, i.e. multiple minutes, is a performance and correctness issue on Android as it keeps the timer module awake, and timers can only be called when the app is in the foreground. See (https://github.com/facebook/react-native/issues/12981) for more info. (Saw setTimeout with duration 111862ms) How Can I Fix That? I don't want to ignore that, I want to understand this error and solve that with the best and Standard way. And This is my Code: [code block] I Asked From Stackoverflow too, Link

Confidence95%
95%
Candidate Fix
1 fix
πŸ”Œ APIs & SDKs
Freshabout 18 hours ago

Vulnerability found

High severity

Confidence95%
95%
Candidate Fix
1 fix
πŸ”Œ APIs & SDKs
Freshabout 18 hours ago

TypeError: axios.get is not a function (v1.1.0)

Describe the bug The new version of axios (v1.1.0) is throwing an error for `axios.get`: `TypeError: axios.get is not a function`. Note: This issue was not present in v1.0.0 To Reproduce Include axio v1.1.0 via a `<script>` tag, and then reference it directly via `axios.get()` [code block] Expected behavior `axios.get` should be a valid function. Environment - Axios Version 1.1.0

Confidence95%
95%
Candidate Fix
1 fix
πŸ”Œ APIs & SDKs
Freshabout 18 hours ago

How to use Axios with TypeScript when using response interceptors (AxiosResponse issue)

Summary In a project I am migrating to TypeScript (TS), I have a response interceptor `r => r.data`. How do I inform TS that I am not expecting a type of `AxiosResponse`? I've tried overriding using `as Array<...` but that doesn't work as `AxiosResponse` can't be cast as an `Array` (e.g. does not has .length). Thanks! Context - axios version: 0.16.2 - Environment: Visual Studio Code

Confidence95%
95%
Candidate Fix
1 fix
πŸ”Œ APIs & SDKs
Freshabout 18 hours ago

Road to Typescript

This is an issue is to discuss our plan to convert this library to TypeScript. Note: We will still continue to provide full Flow typings in the same package. This effort is in line with the ongoing conversion of GraphQL IDE packages (GraphiQL, GraphQL LSP, etc.): https://github.com/graphql/graphiql/tree/convert-to-ts Note this decision is not related to the technical aspect of Flow vs TS. GraphQL.js has complete Flow coverage and it is excellent for ongoing maintenance. But our goal is to increase the number of active contributors and by switching codebase to TypeScript we hope to make the codebase feel more familiar and easy to contribute to. Big thanks to @JacksonKearl from Apollo team for making PoC for such conversion and exploring different conversion strategies. Before we start discussing the action plan here is a few important points: `14.x.x` is stable release so we shouldn't do any potentially breaking things in this release. We need to do `15.0.0` anyway since it becomes hard to maintain support for Node6 since ESLint and other projects stop supporting it. Plus it allows us simply remove all deprecated stuff that was scheduled for removal in this release. Even after we release `15.0.0` we will still need to support `14.x.x` as a branch and backport all critical or security-related bugfixes until `16.0.0`. Giving these constraints here is a plan I want to propose: - [x] 1. Freeze all non-critical merges for the duration of this conversion - [x] 2. I copied al

Confidence95%
95%
Candidate Fix
1 fix
πŸ”Œ APIs & SDKs
Freshabout 18 hours ago

Request params are not getting merged with instance params

Describe the bug Specific request params do not get merged with the instance default params. To Reproduce [code block] [code block] What happens is that the request param object overrides the instance default param object. The instance no longer has a query param of `q`. Expected behavior According to the docs, all configuration options are merged. https://github.com/axios/axios#instance-methods I expected request to contain both `q` and `page` params. This is also how it was working in version 0.18.0, which is how I noticed. Environment: - Axios Version: 0.19.0 - OS: 10.14.5 (18F132) - Browser: Node Express, and Chrome - Browser: Node 10.15.0, Chrome Version 74.0.3729.169 (Official Build) (64-bit)

Confidence95%
95%
Candidate Fix
1 fix
πŸ”Œ APIs & SDKsGoogle
Freshabout 18 hours ago

Google as an Auth provider doesn't work on iOS saved to homescreen

[REQUIRED] Describe your environment Operating System version: iOS 10 Firebase SDK version: 4.1.3 Firebase Product: auth [REQUIRED] Describe the problem Steps to reproduce: 0. Save the app on the homescreen on iOS 1. make a redirect or popup login with google Auth provider 2. if redirect: - webview is not a "valid user agent" 3. if popup: - gets stuck in Safari about:blank, doesn't open the app again to pass on the token Relevant Code: [code block]

Confidence91%
91%
Candidate Fix
1 fix
πŸ”Œ APIs & SDKs
Freshabout 18 hours ago

GraphQL should allow mutating optional fields to 'null'.

Unless I'm overlooking something, I'm not seeing any way to pass `null` into a mutation for an 'optional' arg. It seems that the keys with `null` values get stripped out inside GraphQL-JS itself before making it to my `resolve` in the `obj` parameter.

Confidence90%
90%
Candidate Fix
1 fix
πŸ”Œ APIs & SDKs
Freshover 1 year ago

consider not deprecating typeInfo and getFieldDef options to validate function and TypeInfo constructor

https://github.com/graphql/graphql-js/blob/e1726dfea66979bfe7ad1c0b0834613e4b6ce4b4/src/validation/validate.ts#L44-L45 https://github.com/graphql/graphql-js/blob/e1726dfea66979bfe7ad1c0b0834613e4b6ce4b4/src/utilities/TypeInfo.ts#L66-L67 From what I understand, by preserving these options, we add the ability for a server to add custom meta fields such as `__fulfilled` or `__directive` and still validate properly.

Confidence89%
89%
Candidate Fix
1 fixβœ“ 2 verified
πŸ”Œ APIs & SDKsGoogle
Freshover 6 years ago

AsyncQueue is already failed: The transaction was aborted, so the request cannot be fulfilled.

Describe your environment Operating System version: Android, so the version varies Browser version: Usually latest Chrome (73.0.3683.90) Firebase SDK version: 5.9.3 Firebase Product: Firestore Describe the problem We're seeing the following error more and more lately (via our error reporting service): [code block] This error is of a critical nature, as it entirely breaks the DB layer. ~~Data stops getting written to the database, and it can be somewhat difficult to detect when the DB gets into this state, as the error is only thrown once. You can then call all the DB functions, and everything appears to work as normal, except no data ends up in the cloud (nor the persistence layer).~~ (This was incorrect. Our error collection service just aggregated the data) Steps to reproduce: Apologies, but it's entirely periodic. It could be related to IndexedDB reaching a certain size, as clearing it out seems to postpone the problem for a few weeks. I have no theories as to what causes the "transaction to be aborted". We were hoping the new garbage collection feature would take care of the problem, but so far it doesn't seem like it. The devices running this are of the model "Samsung T580". Any other info you need, let me know.

Confidence89%
89%
Candidate Fix
1 fixβœ“ 1 verified
πŸ”Œ APIs & SDKsTwilio
Freshabout 4 years ago

Dial in Twillio functions keeps calling multiple times

Steps to Reproduce Using the following [code block]` Both numbers get called as expected. The issue is that if I cancel a call on first phone, it starts ringing again until i cancel the call on both or accept on one or timeout happens. Is there a way to prevent that? The statusCallback function is the following, just used to log some extra stuff. [code block]`

Confidence89%
89%
Candidate Fix
1 fixβœ“ 1 verified
πŸ”Œ APIs & SDKsTwilio
Freshalmost 4 years ago

Twilio Verify VerificationCheck is out of date

Issue Summary Calling the following code example present in the Verification docs results in an exception- Code Snippet [code block] Exception/Log [code block] The phone is getting SMS with verification code. Moreover, its verified when checked in the logs on Twilio console, after calling the above function. But this exception makes it impossible for the application to know if the verification succeed or not. Steps to Reproduce 1. Call the verifications.create() method with required parameters to send SMS with code. 2. verificationChecks.create() method with previous phone number and correct code. Technical details: twilio-node version: 3.75.0 node version: 14.17.1

Confidence89%
89%
Candidate Fix
1 fixβœ“ 1 verified
πŸ”Œ APIs & SDKsGoogle
Freshalmost 6 years ago

Error when uploading Youtube video using Electron : Invalid multipart request with 0 mime parts.

This is related to https://github.com/googleapis/google-api-nodejs-client/issues/1083 It seems with the latest versions of googleapis the package switched from using axios to gaxios - this has caused this error to resurface when using the example code on an Electron app. How should this be handled? Environment details - OS: osx - Node.js version: v12.12.0 - npm version: 6.13.0 - `googleapis` version: "googleapis": "^45.0.0", Steps to reproduce 1. Use code from samples/youtube/upload.js inside Electron app 2. Receive `Invalid multipart request with 0 mime parts.` error upon request

Confidence88%
88%
Candidate Fix
1 fixβœ“ 1 verified