All Issues
24,993 verified issues
Plugin [id: 'com.facebook.react.settings'] was not found in any of the following sources
Summary Starting today, running `expo run:android` my build would very quickly fail with [code block] The relevant line (settings.gradle line 4: `plugins { id("com.facebook.react.settings") }`) was recently added to the `expo-template-bare-minimum` package, which the CLI pulls remotely and therefore cannot be versioned by our app. The new plugin (`com.facebook.react.settings`) was apparently introduced in react-native 0.75.0, and then stubbed in 0.74.4 in order to allow Expo to support both 0.74 and 0.75 with Expo 51 (https://github.com/facebook/react-native/pull/45720) I have fixed the problem by updating from react-native 0.74.3 to 0.74.5 (the current recommended version for Expo 51). What platform(s) does this occur on? Android SDK Version 51 Environment expo-env-info 1.2.0 environment info: System: OS: macOS 14.5 Shell: 5.9 - /bin/zsh Binaries: Node: 18.19.1 - /opt/homebrew/opt/node@18/bin/node npm: 10.2.4 - /opt/homebrew/opt/node@18/bin/npm Managers: CocoaPods: 1.15.2 - /opt/homebrew/bin/pod SDKs: iOS SDK: Platforms: DriverKit 23.5, iOS 17.5, macOS 14.5, tvOS 17.5, visionOS 1.2, watchOS 10.5 Android SDK: API Levels: 31, 33, 33, 34 Build Tools: 30.0.3, 33.0.0, 33.0.1, 33.0.2, 34.0.0 System Images: android-32 | Google APIs ARM 64 v8a, android-34 | Google Play ARM 64 v8a IDEs: Android Studio: 2024.1 AI-241.18034.62.2411.12071903 Xcode: 15.4/15F31d - /usr/bin
Should Express 5.0 require a minimum of Node.js 4?
This is a discussion regarding having Express 5.0 drop support for Node.js 0.10. One of the reasons for the delay in Express 5.0 was the announcement of the official merging of Node.js and io.js, and we were looking forward to it's outcome to determine what we should do with Express 5.0. Here at Express, we value very long-lived major versions, allowing users to confidentially build their new server on Express and not have to worry about needing to upgrade across a major, breaking change for years. Express 4.0 has been out for over a year now and Express 3.0 was supported for over 3 years !! When Express 5.0 comes out, Express 4.x line will continue to be fully supported, delivering our users bug fixes, new features, and more! To this end, we have been carefully watching io.js/Node.js in relation to Express 5.0 such that we can continue this great support history without accidentally locking us into the past for a long time. Please share your thoughts here.
request intercepters order is reversed
[code block] which prints: [code block]
How do I handle Vercel preview and Supabase auth?
Hey there. I think this one is massively important and I am unsure why it wasn't an issue before. Nowadays most Continouous Deployments consist of automated deploys. Let it be on render.com on vercel.com or what not. Many of those create a preview URL such as `some-hash.provider.ext` . Now supabase expects a "generic" base URL - which I would like to understand why because from an architectural perspective I think there should be only a list of "allowed URLs" and not necessarily a primary URL as the "primary" term is kinda not helpful (at least I am not seeing the advantage from an outside perspective). Now since the Auth configuration in the UI is very static (input(Main URL), input(additional URLs)) there is no way of having a proper automated workflow - at all. There will always be manual work involved of adding more and more URLs. IMO this can be even considered as "architectural flaw/bug". I'd be happy to help here if you point into the directions that need to be adapted. Other than that I'd be grateful if someone could pick that topic up, it is massively time-consuming and I am having a hard time understanding that this wasn't a problem for other people so far. Discussed in https://github.com/supabase/supabase/discussions/2760 <div type='discussions-op-text'> <sup>Originally posted by pedrobslisboa August 7, 2021</sup> Hey guys, I've been looking for the answer to this question without success. How do I handle Vercel preview and Supabase auth? E.g.: How can I
Failed to execute 'subscribe' on 'PushManager': Subscription failed - no active Service Worker
Operating System MacOS Browser Version All browser Firebase SDK Version 10.2.0 Firebase SDK Product: Messaging Describe your project's tooling Nextjs 13 with Page setup. Example Repo -> https://github.com/2manoj1/nextjs-firebase-example/tree/main Describe the problem Same problem as https://github.com/firebase/firebase-js-sdk/issues/5797 Sometimes calling messaging getToken returns the error: Failed to execute 'subscribe' on 'PushManager': Subscription failed - no active Service Worker. It seems to occur on the first page load and clear storage with unregister sw, when the user refreshes the notifications work and there's no error anymore. <img width="1726" alt="Screenshot 2023-08-21 at 1 45 33 PM" src="https://github.com/firebase/firebase-js-sdk/assets/15128569/d01424c8-c42a-4786-8e63-515bcb1949aa"> Steps and code to reproduce issue - Open https://nextjs-firebase-example.vercel.app/ - Open inspect element - F12 - Clear Storage with Service Worker - Refresh the browser. - See the error. Its coming also first time
Feature request: Typescript definitions for 3.0 API
Please provide Typescript definitions, it makes a world of difference. Currently the 2.0 API bindings are provided for Twilio but not for 3.0.
Vite generates multiple copies of the same stylesheet
Describe the bug I am using the following vite config option to make global styles available in React components without requirement of usage of "@import '../../syles/main" in each component file: [code block] it comes from https://github.com/vitejs/vite/issues/832 My main.scss looks like: [code block] where fonts, colors, breakpoints, animations, layers include global variables. It works fine in part I can use my variables inside component without importing the main SCSS file, but such approach causes an issue that I have multiple copies of the same stylesheet in a head section of page ( see the screenshot: https://imgur.com/a/k6hGnbP ) Reproduction 1. Create empty app (Vite, React, TSX) 2. Create a global main.scss file 3. Import partials _colors.scss and _fonts.scss to main.scss using @import 4. Create vite.config.js with option similar to described in a bug description section 5. Create at least two different components and add it to your App 6. Add some variables to colors.scss and fonts.scss 7. Use variables from colors.scss and fonts.scss in your two components from step 5 using build-in CSS modules support ([component].module.scss) 8. Run your app and look at head section Expected result: There is only one global stylesheet. Actual result: There are multiple copies of global stylesheet, where number of copies equals number of unique components, UPDATE: I've created a simplified app which one reproduces the issue: https://github.com/tastytea-github/vite-global-i
Typeorm CLI not works perfectly after 0.3.0
Issue Description After version 0.3.0 cli does not work perfectly. when I try to create an entity or migration using cli is create entity or migration in the root directory. However, in the old version, it works perfectly. It shows this error with the new version 0.3.0 [code block] Expected Behavior while when I use 0.2.17 version. it works with same command. [code block]
WriteConflict error with MongoDB
Bug description lib/prisma.js - [code block] Using MongoDB free atlas tier, just created database and just connected but getting an error named `WriteConflict` [code block] Last logs [code block] How to reproduce Expected behavior Must create an row with type:`TOTAL_MESSAGES`. Prisma information [code block] an basic event that explains all my code. [code block] Environment & setup - OS: Windows11 64 bit - Database: MongoDB - Node.js version: 16.14.0 Prisma Version [code block]
pre, post middleware are not executed on findByIdAndUpdate
Because a findAndUpdate method is presented to cut down the following code: [code block] to this: [code block] We need to use pre, post middleware exactly the same. At now pre, post middleware are not executed when I make findByIdAndUpdate.
[BUG] `'version' is obsolete`
Description After updating to version v2.25.0, the command `docker compose pull docker-compose.yaml` gives the error `'version' is obsolete` Steps To Reproduce _No response_ Compose Version [code block] Docker Environment [code block] Anything else? _No response_
Entities no longer registered after Hot Reloading
Note from @imnotjames I've edited the title. The most common issue I've seen in this thread relates to the hot-reload feature used by development environments & serverless environments. What happens if that the registered entities are changed by the hot reload with new entities that are no longer registered even if they're similar. If you believe your issue is unrelated to that, please open a new issue with details including a reproducible example. --- Issue type: [ ] question [x ] bug report [ ] feature request [x ] documentation issue Database system/driver: [ ] `cordova` [ ] `mongodb` [ ] `mssql` [ ] `mysql` / `mariadb` [ ] `oracle` [x ] `postgres` [ ] `cockroachdb` [ ] `sqlite` [ ] `sqljs` [ ] `react-native` [ ] `expo` TypeORM version: [ ] `latest` [ ] `@next` [x ] `0.2.24` Been using v0.2.22 and my ormconfig.js is as follows [code block] which works fine, but I updated to v0.2.24 and I'm getting "No repository for \"<entity>\" was found. Looks like this entity is not registered in current \"default\" connection?" when doing a simple query [code block] Is there a documentation I am missing?
Terraform apply hangs indefinitely on AWS VPC deletion
terraform apply hangs forever when trying to destroy an AWS VPC that has dependent resources (security groups, subnets, internet gateways) not managed by the current Terraform state. The AWS API never returns an error β it just waits. The operation must be killed manually. The fix requires identifying and deleting the unmanaged dependent resources first.
PUT and PATCH sending application/x-www-form-urlencoded data
Using 0.5.4 I'm trying to use axios on my front end and fuel on the backend. Fuel Input::patch('param') will give me data from the form request of type patch. This is also true for PUT. Perhaps also POST a.s.o. When I use axios the data is empty and if I use jquery I get my data just fine. [code block] [code block] The difference is if you look at chrome developer tools that jquery sends the data as formData and axios sends the data as json request payload.
AxiosError type for javascript
Summary Axios rejects error with Error type. Adding custom error type will help with distinguishing between axios and other errors. The only way now is to check 'request' field existence which is not always possible. Our internal custom error type has this field too. Example: [code block] Context - axios version: 0.18.0 Relates to: #24
no way to shutdown a server cleanly
Hi, I'm seeking for a way to shutdown a server. The current behavior is, when I call close() on engine, clients disconnect, but connect again immediately. Even if I call socket.io.close() on disconnect, the server is still listening. And, can I suppose if socket.io.close() is called,(and references from my program is all deleted), the socket will be subject to garbage collection? "use strict" var svr = require('socket.io')(12332); var clt1 = require('socket.io-client')('ws://127.0.0.1:12332'); var clt2 = require('socket.io-client')('ws://127.0.0.1:12332'); svr.on('connection', function(socket) { console.log("svr connected"); svr.engine.close(); }); clt1.on('connect', function() { console.log('clt connected'); }); clt1.on('disconnect', function() { console.log('clt disconnected'); // clt1.io.close(); }); clt1.on('error', function() { console.log('clt error'); });
Container queries
Hi, I'm not sure if it's possible already so please forgive if it is. I'll like to implement container queries that are not based on media queries. So in my thinking i'd like to be able specify custom breakpoints (which i know is available) but based on a parent container class rather than a media query. So for example... [code block] I would apply the "thin" class to the container via Javascript.
Couldn't connect to Docker daemon at http+unix://var/run/docker.sock - is it running?
I tried everything in this thread: https://github.com/docker/compose/issues/88 Still no luck. [code block] This is the version: [code block] Any ideas? I also tried installing fig which works right away without any problem...
[Android] Upload package to device fails
I'm trying to build the default example but it fails uploading the package to my device (Android 5.0): Exceptions thrown while deploying. command: `react-native run-android` OS: Linux 15.04 64-bits Log: [code block] sh :app:installDebug FAILED FAILURE: Build failed with an exception. What went wrong: Execution failed for task ':app:installDebug'. > com.android.builder.testing.api.DeviceException: com.android.ddmlib.InstallException: Unable to upload some APKs Try: Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. BUILD FAILED Total time: 20.863 secs Could not install the app on the device, see the error above.[code block]```
Terminal on Windows 7 does not show any text
- VSCode Version: 1.20.0 - OS Version: win7 SP1 X64 Steps to Reproduce: 1.When I use ctrl+~ open the terminal, can't input anything in the terminal 2.And I also find when I right-click a folderοΌ the option [open in the terminal ] is instead of [open in the cmd], but my `"terminal.integrated.shell.window` has been config to powershell.exe 3.It happened after I updated to the latest version. 4.It cannot be solved after restarting the system or vscode. 5.The powershell outside is working normally. Does this issue occur when all extensions are disabled?: Yes