Recently I updated my Mac OS to High Sierra. After the OS update, the Fabric app is not working properly. Not able to generate the "Fastlane beta".
OS Details: Mac OS X: macOS High Sierra (10.13.2)
Fabric Details: App Version: 2.6.17 (1288) Fabric Version: 2.78.0
Environment:
<details><summary>✅ fastlane environment ✅</summary>
### Stack
| Key | Value |
| --------------------------- | ----------------------------------------------- |
| OS | 10.13.2 |
| Ruby | 2.2.4 |
| Bundler? | false |
| Git | git version 2.11.0 (Apple Git-81) |
| Installation Source | /usr/local/lib/fastlane_lib/bundle/bin/fastlane |
| Host | Mac OS X 10.13.2 (17C88) |
| Ruby Lib Dir | /usr/local/lib/fastlane_lib/bundle/lib |
| OpenSSL Version | OpenSSL 1.0.2g 1 Mar 2016 |
| Is contained | false |
| Is homebrew | false |
| Is installed via Fabric.app | true |
| Xcode Path | /Applications/Xcode 8.3.app/Contents/Developer/ |
| Xcode Version | 8.3.3 |
### System Locale
| Variable | Value | |
| -------- | ----------- | - |
| LANG | en_US.UTF-8 | ✅ |
| LC_ALL | en_US.UTF-8 | ✅ |
| LANGUAGE | en_US.UTF-8 | ✅ |
### fastlane files:
**No Fastfile found**
**No Appfile found**
### fastlane gems
| Gem | Version | Update-Status |
| -------- | ------- | -------------- |
| fastlane | 2.78.0 | 💥 Check failed |
### Loaded fastlane plugins:
**No plugins Loaded**
<details><summary><b>Loaded gems</b></summary>
| Gem | Version |
| ------------------------- | ------------ |
| slack-notifier | 2.3.2 |
| CFPropertyList | 2.3.6 |
| claide | 1.0.2 |
| colored2 | 3.1.2 |
| nanaimo | 0.2.3 |
| xcodeproj | 1.5.4 |
| rouge | 2.0.7 |
| xcpretty | 0.2.8 |
| terminal-notifier | 1.8.0 |
| unicode-display_width | 1.3.0 |
| terminal-table | 1.8.0 |
| plist | 3.4.0 |
| public_suffix | 2.0.5 |
| addressable | 2.5.2 |
| multipart-post | 2.0.0 |
| word_wrap | 1.0.0 |
| tty-screen | 0.6.4 |
| tty-cursor | 0.5.0 |
| tty-spinner | 0.8.0 |
| babosa | 1.0.2 |
| colored | 1.2 |
| highline | 1.7.10 |
| commander-fastlane | 4.4.5 |
| excon | 0.60.0 |
| faraday | 0.14.0 |
| unf_ext | 0.0.7.4 |
| unf | 0.1.4 |
| domain_name | 0.5.20170404 |
| http-cookie | 1.0.3 |
| faraday-cookie_jar | 0.0.6 |
| fastimage | 2.1.1 |
| gh_inspector | 1.0.3 |
| json | 1.8.1 |
| mini_magick | 4.5.1 |
| multi_json | 1.13.1 |
| multi_xml | 0.6.0 |
| rubyzip | 1.2.1 |
| security | 0.1.3 |
| xcpretty-travis-formatter | 1.0.0 |
| dotenv | 2.2.1 |
| bundler | 1.16.1 |
| faraday_middleware | 0.12.2 |
| uber | 0.1.0 |
| declarative | 0.0.10 |
| declarative-option | 0.1.0 |
| representable | 3.0.4 |
| retriable | 3.1.1 |
| mime-types-data | 3.2016.0521 |
| mime-types | 3.1 |
| little-plugger | 1.1.4 |
| logging | 2.2.2 |
| jwt | 2.1.0 |
| memoist | 0.16.0 |
| os | 0.9.6 |
| signet | 0.8.1 |
| googleauth | 0.6.2 |
| httpclient | 2.8.3 |
| google-api-client | 0.13.6 |
| libxml-ruby | 3.0.0 |
</details>
*generated on:* **2018-02-01**
</details>
Can anyone please let me know what is the issue on this configuration? Thanks in advance.
EDIT:
I have tried the solution given by #Mike but, I couldn't resolve the issue. Please find the Terminal output,
Last login: Mon Feb 5 16:45:31 on qqvm915 Yuva-M:~ Yuva$ rm -rf
~/.fastlane/bin Yuva-M:~ Yuva$ rm -rf /usr/local/lib/fastlane_lib
Yuva-M:~ Yuva$ cd /Users/Yuva/Documents/iOS\
Applications/TestApp/TestApp\ App/TestApp\ App\ Dev Yuva-M:TestApp
Dev Yuva$ touch Gemfile Yuva-M:TestApp Dev Yuva$ bundle update
Fetching source index from https://rubygems.org/
Retrying fetcher due to error (2/4): Bundler::HTTPError Could not
fetch specs from https://rubygems.org/ Retrying fetcher due to error
(3/4): Bundler::HTTPError Could not fetch specs from
https://rubygems.org/ Retrying fetcher due to error (4/4):
Bundler::HTTPError Could not fetch specs from
https://rubygems.org/Resolving
dependencies............................ Using CFPropertyList 2.3.6
Using public_suffix 2.0.5 Using addressable 2.5.2 Fetching atomos
0.1.2
Your user account isn't allowed to install to the system RubyGems.
You can cancel this installation and run:
bundle install --path vendor/bundle
to install the gems into ./vendor/bundle/, or you can enter your
password and install the bundled gems to RubyGems using sudo.
Password:
Your user account isn't allowed to install to the system RubyGems.
You can cancel this installation and run:
bundle install --path vendor/bundle
to install the gems into ./vendor/bundle/, or you can enter your
password and install the bundled gems to RubyGems using sudo.
Password: Installing atomos 0.1.2 Using babosa 1.0.2 Using bundler
1.16.1 Using claide 1.0.2 Using colored 1.2 Using colored2 3.1.2 Using highline 1.7.10 Using commander-fastlane 4.4.5 Using declarative
0.0.10 Using declarative-option 0.1.0 Using unf_ext 0.0.7.4 Using unf 0.1.4 Using domain_name 0.5.20170404 Using dotenv 2.2.1 Using excon 0.60.0 Using multipart-post 2.0.0 Using faraday 0.14.0 Using http-cookie 1.0.3 Using faraday-cookie_jar 0.0.6 Using
faraday_middleware 0.12.2 Using fastimage 2.1.1 Fetching gh_inspector
1.1.1 Installing gh_inspector 1.1.1 Using jwt 2.1.0 Using little-plugger 1.1.4 Using multi_json 1.13.1 Using logging 2.2.2 Using
memoist 0.16.0 Using os 0.9.6 Using signet 0.8.1 Using googleauth
0.6.2 Using httpclient 2.8.3 Using mime-types-data 3.2016.0521 Using mime-types 3.1 Using uber 0.1.0 Using representable 3.0.4 Using
retriable 3.1.1 Using google-api-client 0.13.6 Fetching json 2.1.0
Installing json 2.1.0 with native extensions Using mini_magick 4.5.1
Using multi_xml 0.6.0 Using plist 3.4.0 Using rubyzip 1.2.1 Using
security 0.1.3 Using slack-notifier 2.3.2 Using terminal-notifier
1.8.0 Using unicode-display_width 1.3.0 Using terminal-table 1.8.0 Using tty-screen 0.6.4 Using tty-cursor 0.5.0 Using tty-spinner 0.8.0
Using word_wrap 1.0.0 Using nanaimo 0.2.3 Fetching xcodeproj 1.5.6
Installing xcodeproj 1.5.6 Using rouge 2.0.7 Using xcpretty 0.2.8
Using xcpretty-travis-formatter 1.0.0 Using fastlane 2.80.0 Bundle
updated! Yuva-M:TestApp Dev Yuva$ bundle exec fastlane beta [✔] 🚀
[17:10:27]: Could not find fastlane in current directory. Make sure to
have your fastlane configuration files inside a folder called
"fastlane". Would you like to set fastlane up? (y/n) y [✔] Looking for
iOS and Android projects in current directory... [17:10:34]: Created
new folder './fastlane'. [17:10:34]: Detected an iOS/macOS project in
the current directory: 'TestApp.xcworkspace' [17:10:34]:
----------------------------- [17:10:34]: --- Welcome to fastlane 🚀 --- [17:10:34]: ----------------------------- [17:10:34]: fastlane can help you with all kinds of automation for your mobile app [17:10:34]:
We recommend automating one task first, and then gradually automating
more over time [17:10:34]: What would you like to use fastlane for?
1. 📸 Automate screenshots
2. 👩✈️ Automate beta distribution to TestFlight
3. 🚀 Automate App Store distribution
4. 🛠 Manual setup - manually setup your project to automate your tasks ?
Fastlane folder generated into project directory but, no file were there. I just tried to generate a build from "Fabric" Mac App, still am getting the error (Find the screenshot.) Any guidance? Thanks.
Mike from Fabric. I'd recommend switching from fastlane in Fabric to using it independently. Here's how to do it, referenced from Felix Krause.
In terminal, run:
rm -rf ~/.fastlane/bin
-- This removes the current fastlane installation from your home directory.
rm -rf /usr/local/lib/fastlane_lib
-- This removes the current fastlane installation from your system.)
After, edit your ~/.bashrc or ~/.bash_profile and remove any reference to fastlane. We're clearing everything out so that you can set up a fresh install.
Now, navigate to your project directory and run touch Gemfile. Add the following content to that file:
source "https://rubygems.org"
gem "fastlane"
Save the file and run bundle update. Commit both the Gemfile and the Gemfile.lock to version control and from now on, every time you run fastlane, prefix your command using bundle exec:
bundle exec fastlane beta
Finally, restart the Fabric macOS app and you'll be all set.
Related
Trying to install build-tools;30.0.03 in debian:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 11 (bullseye)
Release: 11
Codename: bullseye
$ sdkmanager --install "build-tools;30.0.3" --sdk_root=$ANDROID_SDK_ROOT --verbose
Info: Parsing /opt/android-sdk/build-tools/30.0.2/package.xml
Info: Parsing /opt/android-sdk/build-tools/31.0.0/package.xml
Info: Parsing legacy package: /opt/android-sdk/cmdline-tools/7583922
Info: Parsing /opt/android-sdk/emulator/package.xml
Info: Parsing /opt/android-sdk/extras/android/m2repository/package.xml
Info: Parsing /opt/android-sdk/extras/google/m2repository/package.xml
Info: Parsing /opt/android-sdk/patcher/v4/package.xml
Info: Parsing /opt/android-sdk/platform-tools/package.xml
Info: Parsing /opt/android-sdk/platforms/android-30/package.xml
Info: Parsing /opt/android-sdk/platforms/android-31/package.xml
Info: Parsing /opt/android-sdk/system-images/android-30/default/x86_64/package.xml
Info: Parsing /opt/android-sdk/system-images/android-30/google_apis/x86/package.xml
Info: Parsing /opt/android-sdk/system-images/android-31/default/x86_64/package.xml
Info: Parsing /opt/android-sdk/tools/package.xml
Info: Preparing "Install Android SDK Build-Tools 30.0.3 (revision: 30.0.3)".
Warning: Failed to read or create install properties file.
But the package is not installed:
$ sdkmanager --list_installed
Installed packages:=====================] 100% Fetch remote repository...
Path | Version | Description | Location
------- | ------- | ------- | -------
build-tools;30.0.2 | 30.0.2 | Android SDK Build-Tools 30.0.2 | build-tools/30.0.2
emulator | 30.9.5 | Android Emulator | emulator
extras;android;m2repository | 47.0.0 | Android Support Repository | extras/android/m2repository
extras;google;m2repository | 58 | Google Repository | extras/google/m2repository
patcher;v4 | 1 | SDK Patch Applier v4 | patcher/v4
platform-tools | 31.0.3 | Android SDK Platform-Tools | platform-tools
platforms;android-30 | 3 | Android SDK Platform 30 | platforms/android-30
system-images;android-30;google_apis;x86 | 10 | Google APIs Intel x86 Atom System Image | system-images/android-30/google_apis/x86
If I tried different sdk_root=$ANDROID_SDK_ROOT/build-tools, then I got a request to accept the license. But after accept it, the package wasn't installed neither.
January 16, 2019
---------------------------------------
Accept? (y/N): y
Info: Preparing "Install SDK Patch Applier v4 (revision: 1)".
Warning: Failed to read or create install properties file.
Have to run sdkmanager in sudo mode.
$ sudo sdkmanager --install "build-tools;30.0.3" --sdk_root=$ANDROID_SDK_ROOT --verbose
[sudo] password for <debian>:
sudo: sdkmanager: command not found
But command above went wrong, because running a command that is known to exist in a folder that is in a $PATH but fails when attempting to execute with sudo. So I login as root sudo su and run the command above. You can also try one of solutions here to pass env var for sudoers.
I am trying to make an initial build of a PWA (Progressive Web App) that is vanilla JS/HTML/CSS using using TWA (Trusted Web Activity) and Bubblewrap, but get the message cli ERROR spawn jarsigner ENOENT
The $ bubblewrap init --manifest=https://my-pwa.com/manifest.json step was seemingly successful.
However, when I go to build the project I get the following:
$ bubblewrap build
,-----. ,--. ,--. ,--.
| |) /_,--.,--| |-.| |-.| |,---.,--. ,--,--.--.,--,--.,---.
| .-. | || | .-. | .-. | | .-. | |.'.| | .--' ,-. | .-. |
| '--' ' '' | `-' | `-' | \ --| .'. | | \ '-' | '-' '
`------' `----' `---' `---'`--'`----'--' '--`--' `--`--| |-'
`--'
Please, enter passwords for the keystore /home/my-user/AndroidStudioProjects/android.keystore and alias android.
? Password for the Key Store: ***************
? Password for the Key: ***************
Building the Android App...
- Generated Android APK at ./app-release-signed.apk
cli ERROR spawn jarsigner ENOENT
Further context:
$ bubblewrap doctor
doctor Your jdkpath and androidSdkPath are valid.
$ node -v
v19.3.0
$ printf "%s\n" $PATH
/home/my-user/.local/share/nvm/v19.3.0/bin
/usr/local/sbin
/usr/local/bin
/usr/sbin
/usr/bin
/sbin
/bin
/usr/games
/usr/local/games
/snap/bin
/snap/bin
$cat ~/.bubblewrap/config.json
{"jdkPath":"/usr/lib/jvm/default-java/","androidSdkPath":"/home/my-user/Android/Sdk/"}
Answers or any clues on where to investigate next appreciated, thanks.
My issue was resolved by putting a copy of OpenJDK 11 within my home directory and updating the jdkPath in /home/my-user/.bubblewrap/config.json with its location: {"jdkPath":"/home/my-user/Android/jdk-11.0.17+8","androidSdkPath":"/home/my-user/Android/Sdk/"}
I have a cloud-sql postgres11 instance on GCP and use pg_repack cron for cleaning my database. I've noticed that since last maintenance occurred (7th of March 21) I cannot perform a repack.
When tried to manually run a repack I encountered this error message:
ERROR: pg_repack failed with error: program 'pg_repack 1.4.4' does not match database library 'pg_repack 1.4.6'
Did the following checks:
what is the version of pg_repack loaded:
List of installed extensions
Name | Version | Schema | Description
--------------------+---------+------------+--------------------------------------------------------------
pg_repack | 1.4.4 | public | Reorganize tables in PostgreSQL databases with minimal locks
pg_stat_statements | 1.6 | public | track execution statistics of all SQL statements executed
plpgsql | 1.0 | pg_catalog | PL/pgSQL procedural language
(3 rows)
what is the available version of pg_repack:
name | version | installed | superuser | relocatable | schema | requires | comment
-----------+---------+-----------+-----------+-------------+--------+----------+--------------------------------------------------------------
pg_repack | 1.4.4 | t | t | f | | | Reorganize tables in PostgreSQL databases with minimal locks
(1 row)
I upgraded pg_repack to version 1.4.6 and it did not help, I also tried to drop and create the extension, or restart the sql-instance with no luck. :-(
I wonder if someone had encouctered this issue. If so, is there any solution?
I got this working on Debian 10 with a very jank workaround. Basically I built a copy of 1.4.6 with the version checks commented out, and successfully ran it with the -k flag:
sudo apt install build-essential postgresql-server-dev-13 libssl-dev zlib1g-dev libreadline-dev
git clone https://github.com/yunyu/pg_repack.git # My fork with the version checks commented out
cd pg_repack
make && sudo make install
./bin/pg_repack <flags>
It seemed to work and I haven't run into any issues. Obviously run this on a VM that can access the Postgres instance, since you need shell access to even execute pg_repack.
Upgrade the extension:
ALTER EXTENSION pg_repack UPDATE;
I'm encountering an error when trying to do migrations bootstrap for kong, can anyone please help?
serene#ubuntu:~$ sudo kong migrations bootstrap -c /etc/kong/kong.conf --v
2020/10/19 02:21:04 [verbose] Kong: 2.1.4
2020/10/19 02:21:04 [verbose] reading config file at /etc/kong/kong.conf
2020/10/19 02:21:04 [verbose] prefix in use: /usr/local/kong
Error:
/usr/local/share/lua/5.1/kong/cmd/migrations.lua:95: [PostgreSQL error] failed to retrieve PostgreSQL server_version_num: Transport endpoint is not connected
stack traceback:
[C]: in function 'assert'
/usr/local/share/lua/5.1/kong/cmd/migrations.lua:95: in function 'cmd_exec'
/usr/local/share/lua/5.1/kong/cmd/init.lua:88: in function </usr/local/share/lua/5.1/kong/cmd/init.lua:88>
[C]: in function 'xpcall'
/usr/local/share/lua/5.1/kong/cmd/init.lua:88: in function </usr/local/share/lua/5.1/kong/cmd/init.lua:45>
/usr/local/bin/kong:9: in function 'file_gen'
init_worker_by_lua:50: in function <init_worker_by_lua:48>
[C]: in function 'xpcall'
init_worker_by_lua:57: in function <init_worker_by_lua:55>
I am using WSL, Ubuntu 18.04 LTS, I've installed kong v2.1.4, postgresql 12 on it
serene#ubuntu:~$ kong version
2.1.4
serene#ubuntu:~$ dpkg -l | grep postgres
ii pgdg-keyring 2018.2 all keyring for apt.postgresql.org
ii postgresql-12 12.4-1.pgdg18.04+1 amd64 object-relational SQL database, version 12 server
ii postgresql-client-12 12.4-1.pgdg18.04+1 amd64 front-end programs for PostgreSQL 12
ii postgresql-client-common 220.pgdg18.04+1 all manager for multiple PostgreSQL client versions
ii postgresql-common 220.pgdg18.04+1 all PostgreSQL database-cluster manager
I have started the postgresql service.
I have configured kong.conf as follows
database = postgres
pg_host = 127.0.0.1
pg_port = 5433
pg_timeout = 5000
pg_user = kong
pg_password = kong
pg_database = kong
pg_ssl = off
pg_ssl_verify = off
pg_max_concurrent_queries = 0
pg_semaphore_timeout = 60000
I have also configured a user in postgres called kong with password 'kong' as owner of database called 'kong.
serene#ubuntu:~$ sudo -u postgres psql
psql (12.4 (Ubuntu 12.4-1.pgdg18.04+1))
Type "help" for help.
postgres=# \l
List of databases
Name | Owner | Encoding | Collate | Ctype | Access privileges
-----------+----------+----------+---------+---------+-----------------------
kong | kong | UTF8 | C.UTF-8 | C.UTF-8 | =Tc/kong +
| | | | | kong=CTc/kong
postgres | postgres | UTF8 | C.UTF-8 | C.UTF-8 |
template0 | postgres | UTF8 | C.UTF-8 | C.UTF-8 | =c/postgres +
| | | | | postgres=CTc/postgres
template1 | postgres | UTF8 | C.UTF-8 | C.UTF-8 | =c/postgres +
| | | | | postgres=CTc/postgres
(4 rows)
postgres=#
Initially I was using WSL Ubuntu 20.04, Kong 2.1.4, Postgresql 13. Same error.
Did a fresh install of those. Same error.
Deleted Ubuntu 20.04 and installed Ubuntu 18.04 and reinstall Kong 2.1.4 and Postgresql 13. Same error.
Heard someone had troubles with Postgresql 13 when installing Kong, so I went and did a fresh install for Postgresql 12, still same error.
Is there anyone who knows what went wrong and how I can rectify this?
in /etc/mysql/my.cnf:
[mysqld]
log_bin=mysql-bin
binlog_format=ROW
server-id=11
then on mysql client:
mysql> show variables like '%binlog%';
+-----------------------------------------+----------------------+
| Variable_name | Value |
+-----------------------------------------+----------------------+
| binlog_cache_size | 32768 |
| binlog_checksum | CRC32 |
| binlog_direct_non_transactional_updates | OFF |
| binlog_format | STATEMENT |
| binlog_max_flush_queue_time | 0 |
| binlog_order_commits | ON |
| binlog_row_image | FULL |
| binlog_rows_query_log_events | OFF |
| binlog_stmt_cache_size | 32768 |
| innodb_api_enable_binlog | OFF |
| innodb_locks_unsafe_for_binlog | OFF |
| max_binlog_cache_size | 18446744073709547520 |
| max_binlog_size | 1073741824 |
| max_binlog_stmt_cache_size | 18446744073709547520 |
| sync_binlog | 0 |
+-----------------------------------------+----------------------+
15 rows in set (0.00 sec)
I have googled "my.cnf dont take effect" and got "Changes to my.cnf don't take effect (Ubuntu 16.04, mysql 5.6)"
Changes to my.cnf don't take effect (Ubuntu 16.04, mysql 5.6)
I have tested the two answers. But when I start mysql with sudo service mysql start, there always be this error:
/etc/init.d/mysql[27197]: 0 processes alive and '/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf ping' resulted in
/etc/init.d/mysql[27197]: [61B blob data]
/etc/init.d/mysql[27197]: error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)'
/etc/init.d/mysql[27197]: Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!
/etc/init.d/mysql[27197]:
mysql[26527]: ...fail!
systemd[1]: mysql.service: Control process exited, code=exited status=1
systemd[1]: Failed to start LSB: Start and stop the mysql database server daemon.
I have spent two days searching answers, and still not find nothing helpful. Could any one please help me out? Thank you!
Reinstall MySQL
Clean MySQL according to :
https://askubuntu.com/questions/172514/how-do-i-uninstall-mysql
sudo apt-get purge mysql-server mysql-client mysql-common mysql-server-core-* mysql-client-core-*
sudo rm -rf /etc/mysql /var/lib/mysql
sudo apt-get autoremove
sudo apt-get autoclean
as well as https://www.jianshu.com/p/c76b31df5d09
dpkg -l |grep ^rc|awk '{print $2}' |sudo xargs dpkg -P
Install by sudo apt-get install mysql-server-5.6
Make changes in my.cnf take effect
Second answer by Keeth(user:20588) on
Changes to my.cnf don't take effect (Ubuntu 16.04, mysql 5.6)
Configure binlog by editing /etc/mysql/my.cnf
[mysqld]
log_bin=mysql-bin
binlog_format=ROW
server-id=11