woffice-updater | Woffice-Updater | Build Tool library

When enabling hermes in the Podfile and rebuilding the build it fails due to RCT-Folly. No idea what it does.

To re-initialise everything I use the following:

rm -rf node_modules && rm package-lock.json && npm install && cd ios && rm -rf Pods && rm Podfile.lock && pod deintegrate && pod setup && pod install && cd ..

I also start the metro bundler with:

npx react-native --reset-cache

Anyone has a solution?

The app uses react-native v0.64 and we want to have a better performance using hermes.

All information:

ios/Podfile

I am creating an MSI installer with Wix and wrote a task in the azure DevOps pipeline which builds the MSI solution file using MSBuild. When the code is pushed to remote the pipeline runs the task but my task returns the error saying WiX toolset is not installed hence the build fails. Though it is assured that the MSBuild task works as it is building other projects in the solution.

Android Studio Bumblebee (2021.1.1) was released stably on 25 January 2022 bundled with a new Device Manager (accompanying new support for Android 11+ device debugging over WIFI). I jumped on this stable release, updating from Android Studio Arctic Fox (2020.3.1 Patch 4).

Unfortunately however, since updating, physical devices/handsets don't remain connected to Android Studio for the purpose of debugging. I can confirm that the issue was introduced from Android Studio Bumblebee onwards (occurring in Beta and Canary builds also). I've reproduced the issue on Android Studio Bumblebee (Stable), Chipmunk (Beta), and Dolphin (Canary), but Android Studio Arctic Fox (superseded Stable) continues to work just fine.

The issue occurs soon after opening Android Studio (Bumblebee+) with one of my physical devices connected. Everything appears fine initially and I may even have enough time to deploy my project to the handset, before the device disappears from Android Studio (as if I'd physically disconnected the USB cable from my computer or from the handset itself).

I've tried a fair few things in an attempt to determine a root cause. These include testing:

• With different USB cables.
• With different handsets (both varying makes and models).
• With various versions of the Android Studio IDE (as mentioned above).
• Plugging the USB cables into different USB ports on my computer.
• Rebooting handsets and my computer.
• Restarting Android Studio.
• Invalidating caches and restarting Android Studio.
• adb kill-server then adb start-server.
• Revoking/reaccepting USB debugging authorization.
• Reinstalled build tools/platform tools, and ADB.
• A great number of further possibilities, to no avail.

I searched and read through remotely similar issues, including (but not limited to) these:

• Android Studio Arctic Fox (Adb) - Connected Devices are being disconnected after some time
• Android debugger continually disconnects

This particular comment in one of the above issues clued me onto a possible root cause:

I have been fighting for a few days with adb not seeing my device. After trying many other posted solutions, I discovered that the issue was with Chrome also trying to connect its debugger to a web view. If Chrome is connected using chrome://inspect, then adb seems to disconnect. Quitting Chrome resolves the issue. Then I can connect with Android Studio and then restart Chrome and reconnect. Hope this helps someone else.

However I've been unable to do anything with the above discovery, other than close Google Chrome, and hope for the best. Obviously this isn't an ideal solution. It appears as though the moment Google Chrome shows the connected physical device in the chrome://inspect/#devices page, the physical device promptly becomes unavailable through Android Studio.

I've jumped back to Android Studio Arctic Fox (2020.3.1 Patch 4) for the moment, however this brings with it other issues (my current core project targets the latest SDK version, which requires the updated IDE).

Absolutely any help with this would be insanely appreciated. I've exhausted just about every avenue that I can think of!

Alright I have a package Pythran which is a Python to C++ (PYD module) complier. The package itself on conda-forge says it requires clang and clangxx. BUT I have MS Build Tools clang-12 already installed, so these packages are not used at all.

Now every time I go to conda install [package_name] it tells me my environment is inconsistent, because I force removed the clang libraries I don't need (or want) via a:

I get this Error when I try to install Pyodbc , I have already install visual studio and I have Microsoft Visual C++ 12 , 15-19 in my machine but still its giving this error.

I have a QObject derived class Expense that I use in QML like this.

Building my app using flutter on android studio, and when I upload my app bundle (made via flutter build appbundle, the message pops up:

I am first time using function pointers and ran into a weird problem. I am writing a code for STM32G4xx. The main idea is to transmit and receive data through LPUART. I have implemented simple FSM to handle TX and RX. LPUART configured in DMA interrupt mode. I have typedef the function pointer and declared the three function pointer variables (ISR handles) in main.h file as follow:

I just did a fresh install of windows to clean up my computer, moved everything over to my D drive and installed Python through Windows Store (somehow it defaulted to my C drive, so I left it there because Pycharm was getting confused about its location), now I'm trying to pip install the python-docx module for the first time and I'm stuck. I have a recent version of Microsoft C++ Visual Build Tools installed. Excuse me for any irrelevant information I provided, just wishing to be thorough. Here's what's returning in command: